December 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Updated: (DNA-37) Federate schema information from relational sources

by Brian Carothers (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin.... ] Brian Carothers updated DNA-37: ------------------------------- Attachment: DNA-37_mysql_postgresql.patch Thanks! However, as soon as I started testing against other drivers, I found a few one-off issues. The attached patch gets the connector to a state where it will work with HSQLDB, MySql5, or PostgreSQL8. The Oracle, MS, Sybase, and DB2 JDBC drivers don't seem to be in the JBoss maven repository anymore, so I haven't tested against those yet. The patch adds the support for MySQL and PostgreSQL and fixes two minor problems with the previous patches that Randall had caught, switching JdbcMetadataException to be an unchecked exception and using the more efficient Path.getSegmentsList() instead of Path.getSegmentsAsArray() in JdbcMetadataRepository.getNode(Path). > 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: Brian Carothers > 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, DNA-37_mysql_postgresql.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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-598) Shutting down JcrEngine returns, but leaves idle threads running (preventing shutdown of VM) for 60 seconds

by Randall Hauch (JIRA)

Shutting down JcrEngine returns, but leaves idle threads running (preventing shutdown of VM) for 60 seconds ----------------------------------------------------------------------------------------------------------- Key: DNA-598 URL: https://jira.jboss.org/jira/browse/DNA-598 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.6 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.7 A simple program that configures, starts, uses, and then (properly) shuts down a JcrEngine will work correctly, but the VM will not exit for roughly 60 seconds after the engine is shutdown. A stack dump shows that there are several running (but idle) worker threads. -- 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

16 years, 4 months

2
5
0 / 0

[JBoss JIRA] Updated: (DNA-37) Federate schema information from relational sources

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-37: ----------------------------- Assignee: Brian Carothers (was: Sergiy Litsenko) Committed Brian's patches (with only minor modification). This is a great to have this connector working and in the release. Nice job, Brian! > 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: Brian Carothers > 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (DNA-37) Federate schema information from relational sources

by Randall Hauch (JIRA)

[ 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (DNA-37) Federate schema information from relational sources

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-37: ----------------------------- Attachment: DNA-37_deletes_and_project_pom.patch > 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (DNA-37) Federate schema information from relational sources

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-37: ----------------------------- Attachment: DNA-37_graph_changes.patch > 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (DNA-37) Federate schema information from relational sources

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-37: ----------------------------- Attachment: DNA-37_jdbc_meta_connector.patch > 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-564) Move Eclipse plugin code outside of the Maven modules

by Randall Hauch (JIRA)

Move Eclipse plugin code outside of the Maven modules ----------------------------------------------------- Key: DNA-564 URL: https://jira.jboss.org/jira/browse/DNA-564 Project: DNA Issue Type: Task Components: Tools Affects Versions: 0.7 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker Fix For: 0.7 As it stands now in its current location, the Eclipse plugin projects are not Mavenized and thus cannot be easily integrated into the Maven build. Plus, the release process is made much more complex in the current form, because the Eclipse plugin would depend on the Maven artifacts (in released form). Therefore, we should move the Eclipse plugin source code outside of the http://anonsvn.jboss.org/repos/dna/trunk/ area of SVN and into a new http://anonsvn.jboss.org/repos/dna/eclipse/trunk area. See also this email discussion thread: http://lists.jboss.org/pipermail/dna-dev/2009-November/000853.html -- 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

16 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (DNA-589) The JcrRepository.Option.UPDATE_INDEXES_SYNCHRONOUSLY has no effect

by Randall Hauch (JIRA)

The JcrRepository.Option.UPDATE_INDEXES_SYNCHRONOUSLY has no effect ------------------------------------------------------------------- Key: DNA-589 URL: https://jira.jboss.org/jira/browse/DNA-589 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.7 Reporter: Randall Hauch Fix For: 1.0 JcrRepository instances can be configured with the UPDATE_INDEXES_SYNCHRONOUSLY option to specify whether the search indexes should be updated asynchronously or synchronously. Because of DNA-588, the option value has no effect, and all updates to the search indexes are made asynchronously. As soon as DNA-588 is fixed, this issue should be fixed with no other changes. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-583) The In-Memory connector.execute(...) method is not 'all-or-nothing'

by Randall Hauch (JIRA)

The In-Memory connector.execute(...) method is not 'all-or-nothing' ------------------------------------------------------------------- Key: DNA-583 URL: https://jira.jboss.org/jira/browse/DNA-583 Project: DNA Issue Type: Sub-task Components: Connectors Reporter: Randall Hauch Priority: Blocker Maybe the easiest way to correct this is to record the MapNode objects before they are changed, and then if a rollback occurs, to replace the newly-changed MapNode objects with the original. This is a bit more complicated, since individual MapNode methods are called to change the node. -- 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

16 years, 4 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues December 2009