[
https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin....
]
Randall Hauch commented on DNA-37:
----------------------------------
Updated three patch files created by BCar (who is currently having login issues) that
restructure this connector. From Brian:
- DNA-37_deletes_and_project_pom.patch - Deletes the existing dna-common-jdbc project and
substantially all of the existing files in the dna-connector-metadata project. At the
very bottom, it also makes changes to the master project pom, removing the reference to
the dna-common-jdbc module and making all of the JDBC driver JARs be test-scoped so that
we don't end up with a compile time dependency in all of our projects (we currently
do, I checked). I also accidentally commented out the dna-sequencer-java module.
That's unintentional, but it seems safer to let you not patch that one line than to
try to redo the whole patch file.
- DNA-37_graph_changes.patch - Adds a new read-only path-based repository framework. This
is intended to complement the map repository framework, although it does not yet support
writes. The patch also corrects a minor error that I caught in the name of one of the
messages.
- DNA-37_jdbc_meta_connector.patch - Adds the JDBC metadata connector itself along with
its associated tests. The patch is surprisingly lengthy (due mostly to the large number
of configurable properties on the source), but its conceptually very simple. The
JdbcMetadataSource is patterned after the JpaSource, but it creates a
PathRepositoryConnection instead of a MapRepositoryConnection. The JdbcPathRepository is
persistent across connections (like the InfinispanRepository, JBossCacheRepository,
InMemoryRepository, and InMemoryRepository, but unlike the SimpleJpaRepository), and
provides an internal class that implements the PathWorkspace interface to do the bulk of
the connector-specific work. This class has 1 method each for creating the 8 different
node types (root node, catalog node, schema node, tables node, table node, column node,
procedures node, procedure node).
Federate schema information from relational sources
---------------------------------------------------
Key: DNA-37
URL:
https://jira.jboss.org/jira/browse/DNA-37
Project: DNA
Issue Type: Feature Request
Components: Connectors
Reporter: Randall Hauch
Assignee: Sergiy Litsenko
Priority: Minor
Fix For: 1.1
Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch,
DNA-37_jdbc_meta_connector.patch
Create a connector for the federation engine that contributes and exposes the database
schema information for a relational database (via JDBC) into the federated repository.
This would make it possible to have a repository provide information about the databases
in an organization. One choice would be whether to import (and copy) the schema
structure, or to provide access to it in real time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira