[JBoss JIRA] (TEIID-2837) Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2837?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2837:
---------------------------------------
Ok it should be better in Beta2.
> Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name
> --------------------------------------------------------------------
>
> Key: TEIID-2837
> URL: https://issues.jboss.org/browse/TEIID-2837
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Cassandra with Teiid 8.6
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
> Fix For: 8.7
>
>
> Teiid doesn't work with KeySpace or Table which contains UpperCase.
> Reference From Cassandra - Using double quote for Case Sensitive KeySpace and Table:
> http://www.datastax.com/docs/1.1/references/cql/CREATE_KEYSPACE
> Exception when try to deploy:
> java.lang.NullPointerException
> at org.teiid.translator.cassandra.metadata.CassandraMetadataProcessor.processMetadata(CassandraMetadataProcessor.java:52)
> at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:100)
> at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:53)
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61)
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:644)
> at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:161)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:605)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:536)
--
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
12 years, 1 month
[JBoss JIRA] (TEIID-2837) Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2837?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2837:
---------------------------------------
Yes, you are correct. It looks like I fat fingered the indexing. That will be corrected shortly.
> Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name
> --------------------------------------------------------------------
>
> Key: TEIID-2837
> URL: https://issues.jboss.org/browse/TEIID-2837
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Cassandra with Teiid 8.6
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
> Fix For: 8.7
>
>
> Teiid doesn't work with KeySpace or Table which contains UpperCase.
> Reference From Cassandra - Using double quote for Case Sensitive KeySpace and Table:
> http://www.datastax.com/docs/1.1/references/cql/CREATE_KEYSPACE
> Exception when try to deploy:
> java.lang.NullPointerException
> at org.teiid.translator.cassandra.metadata.CassandraMetadataProcessor.processMetadata(CassandraMetadataProcessor.java:52)
> at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:100)
> at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:53)
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61)
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:644)
> at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:161)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:605)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:536)
--
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
12 years, 1 month
[JBoss JIRA] (TEIID-2837) Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name
by Ivan Chan (JIRA)
[ https://issues.jboss.org/browse/TEIID-2837?page=com.atlassian.jira.plugin... ]
Ivan Chan commented on TEIID-2837:
----------------------------------
I did. And I ran into the following error by using Teiid 8.7 Beta 1:
Caused by: org.teiid.translator.TranslatorException: TEIID22000 Could not find the keyspace metadata.
at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:108)
at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:54)
at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73)
at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:654)
at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:161)
at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:615)
at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:546)
at com.jaspersoft.jasperserver.api.engine.common.virtualdatasourcequery.impl.TeiidVirtualDataSourceQueryServiceImpl.deployVirtualDataSource(TeiidVirtualDataSourceQueryServiceImpl.java:289)
... 152 more
Caused by: org.apache.cassandra.db.KeyspaceNotDefinedException: "PortfolioDemo"
at org.teiid.resource.adapter.cassandra.CassandraConnectionImpl.keyspaceInfo(CassandraConnectionImpl.java:90)
at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:106)
... 160 more
> Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name
> --------------------------------------------------------------------
>
> Key: TEIID-2837
> URL: https://issues.jboss.org/browse/TEIID-2837
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Cassandra with Teiid 8.6
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
> Fix For: 8.7
>
>
> Teiid doesn't work with KeySpace or Table which contains UpperCase.
> Reference From Cassandra - Using double quote for Case Sensitive KeySpace and Table:
> http://www.datastax.com/docs/1.1/references/cql/CREATE_KEYSPACE
> Exception when try to deploy:
> java.lang.NullPointerException
> at org.teiid.translator.cassandra.metadata.CassandraMetadataProcessor.processMetadata(CassandraMetadataProcessor.java:52)
> at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:100)
> at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:53)
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61)
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:644)
> at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:161)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:605)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:536)
--
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
12 years, 1 month
[JBoss JIRA] (TEIID-2837) Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2837?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2837:
---------------------------------------
Use the quoted name in the config.
> Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name
> --------------------------------------------------------------------
>
> Key: TEIID-2837
> URL: https://issues.jboss.org/browse/TEIID-2837
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Cassandra with Teiid 8.6
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
> Fix For: 8.7
>
>
> Teiid doesn't work with KeySpace or Table which contains UpperCase.
> Reference From Cassandra - Using double quote for Case Sensitive KeySpace and Table:
> http://www.datastax.com/docs/1.1/references/cql/CREATE_KEYSPACE
> Exception when try to deploy:
> java.lang.NullPointerException
> at org.teiid.translator.cassandra.metadata.CassandraMetadataProcessor.processMetadata(CassandraMetadataProcessor.java:52)
> at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:100)
> at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:53)
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61)
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:644)
> at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:161)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:605)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:536)
--
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
12 years, 1 month
[JBoss JIRA] (TEIID-2837) Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name
by Ivan Chan (JIRA)
[ https://issues.jboss.org/browse/TEIID-2837?page=com.atlassian.jira.plugin... ]
Ivan Chan commented on TEIID-2837:
----------------------------------
Is this fix included in 8.7 Beta1? It seems like I still can reproduce it using 8.7 Beta1. Thanks.
> Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name
> --------------------------------------------------------------------
>
> Key: TEIID-2837
> URL: https://issues.jboss.org/browse/TEIID-2837
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Cassandra with Teiid 8.6
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
> Fix For: 8.7
>
>
> Teiid doesn't work with KeySpace or Table which contains UpperCase.
> Reference From Cassandra - Using double quote for Case Sensitive KeySpace and Table:
> http://www.datastax.com/docs/1.1/references/cql/CREATE_KEYSPACE
> Exception when try to deploy:
> java.lang.NullPointerException
> at org.teiid.translator.cassandra.metadata.CassandraMetadataProcessor.processMetadata(CassandraMetadataProcessor.java:52)
> at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:100)
> at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:53)
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61)
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:644)
> at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:161)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:605)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:536)
--
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
12 years, 1 month
[JBoss JIRA] (TEIID-2870) Expand "allow-join" extension property on Foreign Key
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2870?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2870:
---------------------------------------
expanded the allow-join property to support:
true (default)
false - disable all joins
inner - allow the join only if the foreign table is on the inner side of the join, which could be an inner/cross/left outer with foreign table on the right
Will update the docs as well.
> Expand "allow-join" extension property on Foreign Key
> -----------------------------------------------------
>
> Key: TEIID-2870
> URL: https://issues.jboss.org/browse/TEIID-2870
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 8.7
>
>
> Currently "allow-join" property on a Foreign Key, defines if the joins based on that Foreign Key that are valid to push to the source or not, when JOIN capability is turned on at translator level. This feature is used in the MongoDB translator to allow JOINS to pushed to source.
> What I have seen is "allow-join" is blanket capability that says it supports all LEFT, RIGHT, INNER and CROSS JOINS. It is useful to define this capability in fine grained manner to allow each kind of JOIN explicitly to control the JOIN behavior.
> The need came from MongoDB translator, where INNER,LEFT are possible but CROSS and RIGHT are not.
--
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
12 years, 1 month
[JBoss JIRA] (TEIID-2881) Add support to use DSL when querying remote JDG 6.2
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2881?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-2881:
------------------------------------
Posted question to Infinispan community: https://community.jboss.org/thread/237742
Want to get their feedback/opinion before making further design choices.
I'm asking about their recommendation for metadata driving the building of the queries, because the queries appear to be based on the .proto definition, not the actual java class (which there appears there can be differences).
Ramesh and I discussed the options, and possibility starting with a utility that could produce DDL from .proto file and create .proto from DDL (which could be used to add to designer for import/export). But want to wait to hear from Infinispan group before spending anymore time discussing option.
> Add support to use DSL when querying remote JDG 6.2
> ---------------------------------------------------
>
> Key: TEIID-2881
> URL: https://issues.jboss.org/browse/TEIID-2881
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.7
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> Add support for querying remote JDG 6.2 using DSL.
--
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
12 years, 1 month
[JBoss JIRA] (TEIID-2886) Sybase dependent join IN clause too large
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2886:
-------------------------------------
Summary: Sybase dependent join IN clause too large
Key: TEIID-2886
URL: https://issues.jboss.org/browse/TEIID-2886
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7
If a full set of values (2000) is pushed down and there is any additional bind variables, then the driver will throw an exception.
--
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
12 years, 1 month
[JBoss JIRA] (TEIID-2879) Add more Resource Management
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2879?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2879:
---------------------------------------
There is already some minimal logic to throttle cpu, which is done via the timeslicing property on the engine (if processing exceeds the timeslice, then the plan will be requeued for processing). However this doesn't provide any hard guarantees and isn't based upon any attributes of the query.
A problem we have with any throttling scheme performed on an active basis is that there are other resources that can be held by the plan - source connections and memory (the heap footprint of an inactive plan is typically manageable, but intermediate data spilled to disk can be significant). We have tracking logic already to see what source connections are held by a plan, but we don't track buffer resources to that level (only down to the connection). So without additional tracking logic to be more reactive, we'd have to apply throttling before the plan got started (similar to our max active plans setting).
Active heap throttling is somewhat manageable with the recommendation from the admin guide:
"In systems where large intermediate results are normal (scrolling cursors or sorting over millions of rows) you can consider increasing the max-processing-kb and decreasing the max-reserve-kb so that each request has access to an effectively smaller buffer space."
That is tell Teiid to use a more per plan allocation scheme rather than using a more shared memory pool.
> Add more Resource Management
> ----------------------------
>
> Key: TEIID-2879
> URL: https://issues.jboss.org/browse/TEIID-2879
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Rick Wagner
> Assignee: Steven Hawkins
>
> To protect the system sometimes we may need to throttle the queries to ensure it does not exhaust all the existing resources on the server. Resource management is the key to play this role of monitoring and throttling queries. Oracle products offer such a feature for managing the consumption of resources. We have quite a number of (Teiid) profiles running on a big box and we want to ensure no silly queires are hogging on to all the resources and consequently causing issue to others.
> Ability to throttle the query by restricting query that uses
> 1) Too much CPU
> 2) Too much java heap
> 3) Long running query
--
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
12 years, 1 month