[JBoss JIRA] (TEIID-4936) Add to tool to generate Couchbase ddl
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4936?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-4936:
------------------------------------
Do you think if add another property 'LocalSchemaFile' to control export ddl use DDLStringVisitor is fine? the con is need dependencies change,
can we raise engine's DDLStringVisitor to api? or develop a similiar function util,? so we can export ddl in translator for couchbase, mongodb, etc, especially, in future, if run teiid via spring boot/wildfly sawrm _ ddl.sql.
> Add to tool to generate Couchbase ddl
> --------------------------------------
>
> Key: TEIID-4936
> URL: https://issues.jboss.org/browse/TEIID-4936
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 9.3
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Priority: Optional
> Fix For: 10.x
>
>
> The tools can generate ddl.sql, base one some default properties, like sampleSize, sampleKeyspaces, typedNameList, etc,
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4928) Couchbase - NAMEINSOURCE required for all the columns and tables
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4928?page=com.atlassian.jira.plugin... ]
Kylin Soong resolved TEIID-4928.
--------------------------------
Resolution: Done
Set to resolve due to add a document to note name in source are necessary, feel free re-edit the docs.
> Couchbase - NAMEINSOURCE required for all the columns and tables
> ----------------------------------------------------------------
>
> Key: TEIID-4928
> URL: https://issues.jboss.org/browse/TEIID-4928
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.3
> Reporter: Juraj Duráni
> Assignee: Kylin Soong
>
> Option *NAMEINSOURCE* is de facto required for all the columns and tables. If it is not present then:
> # column name in source query is not enclosed in back quotes - e.g. *`$cb_t1`.ShortValue* instead of *`$cb_t1`.`ShortValue`*
> # name of the table is not added to the source query - e.g. *SELECT ... FROM null `$cb_t1` LET ... WHERE ...* instead of *SELECT ... FROM `smalla` `$cb_t1` LET ... WHERE ...*
> This should work OOB without need to add NAMEINSOURCE option. Teiid should automatically translate column name from e.g. *MyColumn* to *`MyColumn`* if option is not set. Same with name of the table.
> In case of table I think this is more serious as it does not even try name of the table but supplies *null* to the query
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4861) ASSERTION FAILED: expected reference to be not null
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-4861?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-4861:
---------------------------------
Fix Version/s: 8.12.11.6_3
> ASSERTION FAILED: expected reference to be not null
> ---------------------------------------------------
>
> Key: TEIID-4861
> URL: https://issues.jboss.org/browse/TEIID-4861
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.0.2, 9.2.1, 9.2.2
> Reporter: Harold Campbell
> Assignee: Steven Hawkins
> Fix For: 9.3, 9.2.3, 8.12.11.6_3
>
> Attachments: DEBUG_LOG, DEBUG_LOG_WORKS
>
>
> I have a vdb containing a multi-source schema (channel) and a single source schema (ops). The following query which uses an aggregate function and groups by both a mulit-source column and a single source column causes the error "TEIID30019 Unexpected exception for request l1HvA1r84nyA.0: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null" and a stack trace which looks quite similar to that in TEIID-4325:
> {code}
> select s.channel, m.user_name, count(*)
> from channel.dbo.service_request s
> join ops.dbo.manager m
> on s.staff_id = m.manager_id
> group by s.channel, m.user_name;
> {code}
> Apr 15 20:09:52 localhost docker[27044]: 2017-04-16 01:09:52,237 ERROR [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue7) l1HvA1r84nyA TEIID30019 Unexpected exception for request l1HvA1r84nyA.0: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.core.util.Assertion.failed(Assertion.java:73)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:367)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:133)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:96)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:91)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:226)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:477)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:349)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:275)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:282)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> Apr 15 20:09:52 localhost docker[27044]: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> Apr 15 20:09:52 localhost docker[27044]: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> Apr 15 20:09:52 localhost docker[27044]: at java.lang.Thread.run(Thread.java:745)
> Interestingly, if I narrow the query down to specific channels the error goes away:
> {code}
> select s.channel, m.user_name, count(*)
> from channel.dbo.service_request s
> join ops.dbo.manager m
> on s.staff_id = m.manager_id
> where channel in ('oak', 'cypress')
> group by s.channel, m.user_name;
> {code}
> I will attach both query plans.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4861) ASSERTION FAILED: expected reference to be not null
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4861?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4861:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1455837
Bugzilla Update: Perform
> ASSERTION FAILED: expected reference to be not null
> ---------------------------------------------------
>
> Key: TEIID-4861
> URL: https://issues.jboss.org/browse/TEIID-4861
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.0.2, 9.2.1, 9.2.2
> Reporter: Harold Campbell
> Assignee: Steven Hawkins
> Fix For: 9.3, 9.2.3
>
> Attachments: DEBUG_LOG, DEBUG_LOG_WORKS
>
>
> I have a vdb containing a multi-source schema (channel) and a single source schema (ops). The following query which uses an aggregate function and groups by both a mulit-source column and a single source column causes the error "TEIID30019 Unexpected exception for request l1HvA1r84nyA.0: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null" and a stack trace which looks quite similar to that in TEIID-4325:
> {code}
> select s.channel, m.user_name, count(*)
> from channel.dbo.service_request s
> join ops.dbo.manager m
> on s.staff_id = m.manager_id
> group by s.channel, m.user_name;
> {code}
> Apr 15 20:09:52 localhost docker[27044]: 2017-04-16 01:09:52,237 ERROR [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue7) l1HvA1r84nyA TEIID30019 Unexpected exception for request l1HvA1r84nyA.0: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.core.util.Assertion.failed(Assertion.java:73)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:367)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:133)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:96)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:91)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:226)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:477)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:349)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:275)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:282)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> Apr 15 20:09:52 localhost docker[27044]: at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> Apr 15 20:09:52 localhost docker[27044]: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> Apr 15 20:09:52 localhost docker[27044]: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> Apr 15 20:09:52 localhost docker[27044]: at java.lang.Thread.run(Thread.java:745)
> Interestingly, if I narrow the query down to specific channels the error goes away:
> {code}
> select s.channel, m.user_name, count(*)
> from channel.dbo.service_request s
> join ops.dbo.manager m
> on s.staff_id = m.manager_id
> where channel in ('oak', 'cypress')
> group by s.channel, m.user_name;
> {code}
> I will attach both query plans.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4928) Couchbase - NAMEINSOURCE required for all the columns and tables
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4928?page=com.atlassian.jira.plugin... ]
Kylin Soong edited comment on TEIID-4928 at 5/26/17 3:19 AM:
-------------------------------------------------------------
> One more note. Keyspace property in resource-adapter. Can you define multiple keyspaces?
Are you means sampleKeyspaces in TEIID-4933?
The Keyspace in resource-adapter are useed to create connection, with couchbase SDK(java client),
* if a connection created against one Keyspace, the connection can operate all documents in a namespace across different keyspaces with lower standard of security. The current implements use this way.
* The connection can create against the Namespaces or higher level abstraction like Datastores, but this need higher standard of security, I think this can be a enhance for future.
was (Author: kylin):
> One more note. Keyspace property in resource-adapter. Can you define multiple keyspaces?
Are you means sampleKeyspaces in TEIID-4933?
The Keyspace in resource-adapter are useed to create connection, with couchbase SDK(java client),
* if a connection against one Keyspace, the connection can operate all documents in different Keyspaces under same namespace, with lower standard of security.
* The connection can create against the Namespaces or higher level abstraction like Datastores, but this need higher standard of security, I think this can be a enhance for future.
> Couchbase - NAMEINSOURCE required for all the columns and tables
> ----------------------------------------------------------------
>
> Key: TEIID-4928
> URL: https://issues.jboss.org/browse/TEIID-4928
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.3
> Reporter: Juraj Duráni
> Assignee: Kylin Soong
>
> Option *NAMEINSOURCE* is de facto required for all the columns and tables. If it is not present then:
> # column name in source query is not enclosed in back quotes - e.g. *`$cb_t1`.ShortValue* instead of *`$cb_t1`.`ShortValue`*
> # name of the table is not added to the source query - e.g. *SELECT ... FROM null `$cb_t1` LET ... WHERE ...* instead of *SELECT ... FROM `smalla` `$cb_t1` LET ... WHERE ...*
> This should work OOB without need to add NAMEINSOURCE option. Teiid should automatically translate column name from e.g. *MyColumn* to *`MyColumn`* if option is not set. Same with name of the table.
> In case of table I think this is more serious as it does not even try name of the table but supplies *null* to the query
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4936) Add to tool to generate Couchbase ddl
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4936?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-4936:
------------------------------------
My main concern is, if don't use Designer, just deploy a vdb.xml with Couchbase Source Model, couchbase connector will generate lots of tables, but the users don't know what exactly generated.
> Add to tool to generate Couchbase ddl
> --------------------------------------
>
> Key: TEIID-4936
> URL: https://issues.jboss.org/browse/TEIID-4936
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 9.3
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Priority: Optional
> Fix For: 10.x
>
>
> The tools can generate ddl.sql, base one some default properties, like sampleSize, sampleKeyspaces, typedNameList, etc,
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4928) Couchbase - NAMEINSOURCE required for all the columns and tables
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4928?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-4928:
------------------------------------
> One more note. Keyspace property in resource-adapter. Can you define multiple keyspaces?
Are you means sampleKeyspaces in TEIID-4933?
The Keyspace in resource-adapter are useed to create connection, with couchbase SDK(java client),
* if a connection against one Keyspace, the connection can operate all documents in different Keyspaces under same namespace, with lower standard of security.
* The connection can create against the Namespaces or higher level abstraction like Datastores, but this need higher standard of security, I think this can be a enhance for future.
> Couchbase - NAMEINSOURCE required for all the columns and tables
> ----------------------------------------------------------------
>
> Key: TEIID-4928
> URL: https://issues.jboss.org/browse/TEIID-4928
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.3
> Reporter: Juraj Duráni
> Assignee: Kylin Soong
>
> Option *NAMEINSOURCE* is de facto required for all the columns and tables. If it is not present then:
> # column name in source query is not enclosed in back quotes - e.g. *`$cb_t1`.ShortValue* instead of *`$cb_t1`.`ShortValue`*
> # name of the table is not added to the source query - e.g. *SELECT ... FROM null `$cb_t1` LET ... WHERE ...* instead of *SELECT ... FROM `smalla` `$cb_t1` LET ... WHERE ...*
> This should work OOB without need to add NAMEINSOURCE option. Teiid should automatically translate column name from e.g. *MyColumn* to *`MyColumn`* if option is not set. Same with name of the table.
> In case of table I think this is more serious as it does not even try name of the table but supplies *null* to the query
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years