January 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2786: ------------------------------------ I was wrong, you were using the updated driver. As that's the same error I'm hitting. Its an issue with Modeshape and its handling of data types. > ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2786 > URL: https://issues.jboss.org/browse/TEIID-2786 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7 > > Attachments: mode.patch > > > When trying to use the Teiid Designer feature of importing using a Teiid Connection fails when the connection is to ModeShape. The following exception: > 08:33:44,914 ERROR [stderr] (teiid-async-threads - 2) java.sql.SQLFeatureNotSupportedException > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.modeshape.jdbc.JcrMetaData.getTypeInfo(JcrMetaData.java:1656) > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:107) > 08:33:44,915 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml") > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:280) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:62) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$6.run(VDBService.java:397) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$7.run(VDBService.java:444) > 08:33:44,918 ERROR [stderr] (teiid-async-threads - 2) at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) > My guess is the local modeshape jdbc driver hasn't been fully vetted in this area, as the remote JDBC version has been the one used when using the Modeshape eclipse plugin for importing the metadata. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2786: --------------------------------------- Made an initial commit based upon the simplified changes. It did include the change to correct the widenUnsignedTypes setter method name. It introduced an import foreign keys options, which we can optional document, and an way to set the column name pattern. Using an older driver I was hitting: java.lang.NumberFormatException: For input string: "org.modeshape.jdbc.JdbcJcrValueFactory$JdbcJcrValue@73abdb5e" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Long.parseLong(Long.java:438) at java.lang.Long.parseLong(Long.java:478) at org.modeshape.jdbc.JcrResultSet.getValueObject(JcrResultSet.java:1302) at org.modeshape.jdbc.JcrResultSet.getValueReturn(JcrResultSet.java:1260) at org.modeshape.jdbc.JcrResultSet.getLong(JcrResultSet.java:851) at org.modeshape.jdbc.JcrResultSet.getInt(JcrResultSet.java:831) at org.modeshape.jdbc.JcrResultSet.getInt(JcrResultSet.java:820) at org.teiid.translator.jdbc.JDBCMetdataProcessor.addColumn(JDBCMetdataProcessor.java:368) at org.teiid.translator.jdbc.JDBCMetdataProcessor.processColumns(JDBCMetdataProcessor.java:352) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getColumns(JDBCMetdataProcessor.java:327) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:278) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:130) when retrieving an integer property as getValueObject doesn't have a handler for integer and it ends up trying to parse the toString of the value. Will need to retest with a later driver to see if this requires another workaround. > ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2786 > URL: https://issues.jboss.org/browse/TEIID-2786 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7 > > Attachments: mode.patch > > > When trying to use the Teiid Designer feature of importing using a Teiid Connection fails when the connection is to ModeShape. The following exception: > 08:33:44,914 ERROR [stderr] (teiid-async-threads - 2) java.sql.SQLFeatureNotSupportedException > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.modeshape.jdbc.JcrMetaData.getTypeInfo(JcrMetaData.java:1656) > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:107) > 08:33:44,915 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml") > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:280) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:62) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$6.run(VDBService.java:397) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$7.run(VDBService.java:444) > 08:33:44,918 ERROR [stderr] (teiid-async-threads - 2) at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) > My guess is the local modeshape jdbc driver hasn't been fully vetted in this area, as the remote JDBC version has been the one used when using the Modeshape eclipse plugin for importing the metadata. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2806) Accumulo Connector: Handling Authorizations with NULL value

by devin pinkston (JIRA)

[ https://issues.jboss.org/browse/TEIID-2806?page=com.atlassian.jira.plugin... ] devin pinkston commented on TEIID-2806: --------------------------------------- You can create Authorizations with no value: Authorizations auths = new Authorizations()); So if you inserted data with that, you can't read from a batchscanner/scanner in accumulo translator. > Accumulo Connector: Handling Authorizations with NULL value > ----------------------------------------------------------- > > Key: TEIID-2806 > URL: https://issues.jboss.org/browse/TEIID-2806 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.7 > Reporter: devin pinkston > Assignee: Steven Hawkins > > Currently the connector cannot handle null authorizations or roles left blank. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2806) Accumulo Connector: Handling Authorizations with NULL value

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2806?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2806: ------------------------------------- Does Accumulo allow "null" role? I did not see any reference that it will allow it. > Accumulo Connector: Handling Authorizations with NULL value > ----------------------------------------------------------- > > Key: TEIID-2806 > URL: https://issues.jboss.org/browse/TEIID-2806 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.7 > Reporter: devin pinkston > Assignee: Steven Hawkins > > Currently the connector cannot handle null authorizations or roles left blank. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2806) Accumulo Connector: Handling Authorizations with NULL value

by devin pinkston (JIRA)

devin pinkston created TEIID-2806: ------------------------------------- Summary: Accumulo Connector: Handling Authorizations with NULL value Key: TEIID-2806 URL: https://issues.jboss.org/browse/TEIID-2806 Project: Teiid Issue Type: Bug Components: Connector API Affects Versions: 8.7 Reporter: devin pinkston Assignee: Steven Hawkins Currently the connector cannot handle null authorizations or roles left blank. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2482) Allow the use of the enhanced join for left outer joins

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2482?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2482: --------------------------------- Fix Version/s: 7.7.9 > Allow the use of the enhanced join for left outer joins > ------------------------------------------------------- > > Key: TEIID-2482 > URL: https://issues.jboss.org/browse/TEIID-2482 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4, 7.7.7, 7.7.9 > > > Left equi outer joins are currently only implemented using the full sort merge join and would benefit from using the enhanced merge when the inner side is relatively small. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2482) Allow the use of the enhanced join for left outer joins

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2482?page=com.atlassian.jira.plugin... ] Johnathon Lee resolved TEIID-2482. ---------------------------------- Resolution: Done added 7.7.9 > Allow the use of the enhanced join for left outer joins > ------------------------------------------------------- > > Key: TEIID-2482 > URL: https://issues.jboss.org/browse/TEIID-2482 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.7.9, 7.7.7, 8.4 > > > Left equi outer joins are currently only implemented using the full sort merge join and would benefit from using the enhanced merge when the inner side is relatively small. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2482) Allow the use of the enhanced join for left outer joins

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2482?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-2482. -------------------------------- > Allow the use of the enhanced join for left outer joins > ------------------------------------------------------- > > Key: TEIID-2482 > URL: https://issues.jboss.org/browse/TEIID-2482 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4, 7.7.7, 7.7.9 > > > Left equi outer joins are currently only implemented using the full sort merge join and would benefit from using the enhanced merge when the inner side is relatively small. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2482) Allow the use of the enhanced join for left outer joins

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2482?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-2482: ---------------------------------- opening to indicate working backport to 7.7.9 > Allow the use of the enhanced join for left outer joins > ------------------------------------------------------- > > Key: TEIID-2482 > URL: https://issues.jboss.org/browse/TEIID-2482 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4, 7.7.7 > > > Left equi outer joins are currently only implemented using the full sort merge join and would benefit from using the enhanced merge when the inner side is relatively small. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2785) Designer needs a way to utilize pushdown functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2785?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2785: ---------------------------------- Summary: Designer needs a way to utilize pushdown functions (was: Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call) Description: Pushdown functions, such as the ones exposed by the ModeShapeExecutionFactory, should be available at design time. (was: The ModeShapeExecutionFactory should expose the JCR procedures in the metadata when the getMetadata(..) is called. ) Assignee: Steven Hawkins (was: Van Halbert) Git Pull Request: (was: https://github.com/teiid/teiid/pull/174) Component/s: Misc. Connectors (was: JDBC Connector) Modifying the issue to something more general about pushdown functions. > Designer needs a way to utilize pushdown functions > -------------------------------------------------- > > Key: TEIID-2785 > URL: https://issues.jboss.org/browse/TEIID-2785 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7 > > > Pushdown functions, such as the ones exposed by the ModeShapeExecutionFactory, should be available at design time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2014