June 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3014) Honor the visibility flags in generation of in OData EDM Schema

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3014?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3014: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Honor the visibility flags in generation of in OData EDM Schema > --------------------------------------------------------------- > > Key: TEIID-3014 > URL: https://issues.jboss.org/browse/TEIID-3014 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: OData > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > Currently when EDM Metadata s generated the visibility flags were not taken into account and generates all the metadata. It should honor the user's configuration about visibility. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3015) ODATA: Duplicate NavigationProperty name

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3015: ----------------------------------- Summary: ODATA: Duplicate NavigationProperty name Key: TEIID-3015 URL: https://issues.jboss.org/browse/TEIID-3015 Project: Teiid Issue Type: Bug Security Level: Public (Everyone can see) Components: OData Affects Versions: 8.3 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 8.7.1, 8.8 Entity 1: TransferRule Entity 2: FinancialAccount TransferRule - sourceAccount : FinancialAccount - destination : FinancialAccount - other attributes the mapping to this for odata resolves to <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" /> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" /> The navigation property name is duplicated with in transfer rule entity. Hence some of the Odata client see it as ambiguous element Is there a way to customise the Name to Name="src_financialaccount" and Name="dest_financialaccount" -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3014) Honor the visibility flags in generation of in OData EDM Schema

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3014: ----------------------------------- Summary: Honor the visibility flags in generation of in OData EDM Schema Key: TEIID-3014 URL: https://issues.jboss.org/browse/TEIID-3014 Project: Teiid Issue Type: Enhancement Security Level: Public (Everyone can see) Components: OData Affects Versions: 8.3 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 8.7.1, 8.8 Currently when EDM Metadata s generated the visibility flags were not taken into account and generates all the metadata. It should honor the user's configuration about visibility. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 8 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 resolved TEIID-2786. ----------------------------------- Fix Version/s: 8.7 (was: 8.7.1) Resolution: Done > ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2786 > URL: https://issues.jboss.org/browse/TEIID-2786 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > 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 was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 8 months

1
0
0 / 0

[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: ------------------------------------ After further testing with the patched jdbc driver provided by ModeShape, I'm no longer seeing this issue. I was to import the metadata, create the VDB, deploy and then query. This is also been verified by a user. So I would consider this fixed, and therefore,reject this jira. > ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2786 > URL: https://issues.jboss.org/browse/TEIID-2786 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7.1 > > 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 was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 8 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2786: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1048948|https://bugzilla.redhat.com/show_bug.cgi?id=1048948] from NEW to MODIFIED > ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2786 > URL: https://issues.jboss.org/browse/TEIID-2786 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7.1 > > 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 was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 8 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2785?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2785: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1045206|https://bugzilla.redhat.com/show_bug.cgi?id=1045206] from NEW to MODIFIED > Designer needs a way to utilize pushdown functions > -------------------------------------------------- > > Key: TEIID-2785 > URL: https://issues.jboss.org/browse/TEIID-2785 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > 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 was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2783) ModeShape query isn't retaining quotes defined for column in NIS

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2783?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2783: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1045206|https://bugzilla.redhat.com/show_bug.cgi?id=1045206] from NEW to MODIFIED > ModeShape query isn't retaining quotes defined for column in NIS > ---------------------------------------------------------------- > > Key: TEIID-2783 > URL: https://issues.jboss.org/browse/TEIID-2783 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Attachments: ModeShape.vdb > > > Issuing query: > SELECT jcr_name FROM nt_base AS children WHERE JCR_ISCHILDNODE(children.jcr_path, '/pathtoparent') > produces exception: > Caused by: javax.jcr.query.InvalidQueryException: The JCR-SQL2 query "SELECT g_0.jcr:name FROM "nt:base" AS g_0 WHERE ISCHILDNODE(g_0.jcr:path, '/pathtoparent')" is not well-formed: Expecting "FROM" but found ":" at line 1, column 15: SELECT g_0.jcr ===>> :name FROM "nt:base" > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:146) > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:101) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2990) MongoDB: Usage of lookup() function throws an exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2990?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2990: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1105121|https://bugzilla.redhat.com/show_bug.cgi?id=1105121] from NEW to MODIFIED > MongoDB: Usage of lookup() function throws an exception > ------------------------------------------------------- > > Key: TEIID-2990 > URL: https://issues.jboss.org/browse/TEIID-2990 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.8 > > Attachments: server.log > > > Exception[1] is thrown when function lookup() is used in SQL query. > Mongo translator doesn't support selection of constants only, which causes the exception(select 1, select 'hi' from smalla). > {code} > [1] 3:59:20,997 ERROR [org.teiid.CONNECTOR] (Worker5_QueryProcessorQueue6) Connector worker process failed for atomic-request=Ef2Z7E0246by.1.5.3: com.mongodb.CommandFailureException: { "serverUsed" : "localhost/127.0.0.1:27017" , "errmsg" : "exception: $projection requires at least one output field" , "code" : 16403 , "ok" : 0.0} > at com.mongodb.CommandResult.getException(CommandResult.java:71) > {code} > Server log is in the attachment. > Sample query: > {code} > SELECT BQT1.SmallA.IntKey FROM BQT1.SmallA, BQT1.SmallB WHERE BQT1.SmallA.IntKey= lookup('BQT1.SmallB', 'IntKey', 'StringKey', BQT1.SmallA.StringKey) ORDER BY IntKey > {code} > Generated mongo commands: > {code} > { aggregate: "smalla", pipeline: [ { $project: { _m0: "$INTKEY", _m1: "$STRINGKEY" } } ] } > {code} > and > {code} > { aggregate: "smallb", pipeline: [ { $project: {} } ] } > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2992) MongoDB: Offset clause causes MongoDB to crash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2992?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2992: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1105473|https://bugzilla.redhat.com/show_bug.cgi?id=1105473] from NEW to MODIFIED > MongoDB: Offset clause causes MongoDB to crash > ---------------------------------------------- > > Key: TEIID-2992 > URL: https://issues.jboss.org/browse/TEIID-2992 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.4.1 > Environment: MongoDB < 2.5.2 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.8 > > > MongoDB(version < 2.5.2) will crash when offset clause is used in SQL query. > Althought the bug[1] is in MongoDB (Adding big number into $limit causes Mongodb to shutdown), it is also caused by teiid because it adds max integer into $limit which seems to be unnecessary. > Sample query: > {code} > SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY OFFSET 45 ROWS > {code} > Generated mongo command: > {code} > { aggregate: "smalla", pipeline: [ { $project: { c_0: "$INTKEY" } }, { $sort: { c_0: 1 } }, { $skip: 45 }, { $limit: 2147483647 } ] } > {code} > [1] https://jira.mongodb.org/browse/SERVER-10136 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2014