[JBoss JIRA] (TEIID-4936) Add to tool to generate Couchbase ddl
by Kylin Soong (JIRA)
Kylin Soong created TEIID-4936:
----------------------------------
Summary: 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, 7 months
[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:
------------------------------------
Hi Juraj Duráni
Thanks for your comments.
Let's back to the original concern, let's add a note in document to address that the recommend way it to use teiid generated schema, if define the schema manually, the NAMEINSOURCE required for all the columns and tables, and also add more content with how de set OPTIONS and rules to define NAMEINSOURCE.
For the suggestion you raised at the end of above comments, I have add a PR(https://github.com/teiid/teiid/pull/963), with this PR, now, you design DDL can avoid add "teiid_couchbase:ISARRAYTABLE" 'false', :). To rename the Option name, there are too much change, especially test related change.
For table name map to keyspace name in couchbase, I would use CustomerOrder example as [1]. Note a json document contain "type": "Customer" exsit in test keysapce. If you define importer property typeNameList values as
{code}
`test`:`type`
{code}
then CouchbaseMetadataProcessor auto-generated ddl as [2], note that the table name is Customer, if you query against it
{code}
SELECT * FROM Customer
{code}
in translator, the query will be translate to
{code}
SELECT ... FROM `test` ...
{code}
Note that you query against table is Customer, but the souce query is against on keyspace test. [3] is the completed source level N1ql. [4] is the embedded CustomerOrder example.
Appreciate you can find more defects, appreciate also you can file new JIRA for new dfects.
Kylin
[1] https://teiid.gitbooks.io/documents/content/reference/couchbase_translato...
[2] https://raw.githubusercontent.com/teiid/teiid/master/connectors/couchbase...
[3] SELECT `$cb_c1_documentID`, `$cb_c2_ID`, `$cb_c3_type`, `$cb_c4_Name` FROM `test` `$cb_t1` LET `$cb_c1_documentID` = META(`$cb_t1`).id, `$cb_c2_ID` = `$cb_t1`.`ID`, `$cb_c3_type` = `$cb_t1`.`type`, `$cb_c4_Name` = `$cb_t1`.`Name` WHERE `$cb_c3_type` = 'Customer'
[4] https://github.com/teiid/teiid-embedded-examples/tree/master/couchbase-as...
> 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, 7 months
[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/25/17 6:05 AM:
-------------------------------------------------------------
> A you saying that we'll need more documentation on how to define the metadata manually? Or are you suggesting that we should reuse the simba schema tools?
* reuse simba schema tools seems has difficult, I prefer to add more documents, probably we add a tools like the teiid-oauth-util.sh, run this tool can generate a ddl,sql or souce-model,xml.
* I added a enhance in TEIID-4933, add another sampleKeyspaces property for limit the scope of keyspaces, if set a smaller scope of keyspaces(only set one or two), then the sampleSize can set a larger value, which can match some of Juraj's expects. TEIID-4933 also add support multiple typed name per keyspace, this can make the table map more fine-grained, in most of times, u the sers may focus on the documents in specific keyspace, supported multiple typed name can better match their requirements.
* I also add more content of documents, but it still not enough.
was (Author: kylin):
> A you saying that we'll need more documentation on how to define the metadata manually? Or are you suggesting that we should reuse the simba schema tools?
simba schema tools seems has difficult, probably we add a tools like the teiid-oauth-util.sh, run this tool can generate a ddl,sql or souce-model,xml. How to define the metadata manually also is lacked.
> 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, 7 months
[JBoss JIRA] (TEIID-4934) Allow importing VDBs with conflicting model
by Pedro Inácio (JIRA)
Pedro Inácio created TEIID-4934:
-----------------------------------
Summary: Allow importing VDBs with conflicting model
Key: TEIID-4934
URL: https://issues.jboss.org/browse/TEIID-4934
Project: Teiid
Issue Type: Enhancement
Affects Versions: 9.2.3
Environment: * Wildfly 10
* Teiid Server 9.2.3
Reporter: Pedro Inácio
Assignee: Steven Hawkins
It should be possible to import a model via "_import-vdb_" that conflicts with other models also imported via "_import-vdb_" if the conflicting model has the same version.
This will allow greater model reuse, and not to have duplicated model definitions in multiple vdbs.
Example:
VDB 1:
<code>
<vdb name="OneVDB" version="1">
<description>One VDB</description>
<import-vdb name=ConflictingVDB" version="1"/>
<import-vdb name="OtherVDB" version="1"/>
</code>
VDB 2:
<code>
<vdb name="TwoVDB" version="1">
<description>TwoVDB</description>
<import-vdb name=ConflictingVDB" version="1"/>
<import-vdb name="YetOtherVDB" version="1"/>
</code>
VDB 3:
<code>
<vdb name="ThirdVDB" version="1">
<description>Third VDB</description>
<import-vdb name=OneVDB" version="1"/>
<import-vdb name="TwoVDB" version="1"/>
</code>
Currently we cannot use the ThirdVDB as is, since there is a conflicting VDB (ConflictingVDB) defined in VDBS One and Two.
Since both are using the same version, it should be possible to ignore the conflict (via a property for example).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (TEIID-4931) No Deployed Virtual Databases on console
by Pedro Inácio (JIRA)
[ https://issues.jboss.org/browse/TEIID-4931?page=com.atlassian.jira.plugin... ]
Pedro Inácio updated TEIID-4931:
--------------------------------
Attachment: list-vdbs-result.json
> No Deployed Virtual Databases on console
> ----------------------------------------
>
> Key: TEIID-4931
> URL: https://issues.jboss.org/browse/TEIID-4931
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.2.3
> Environment: * Wildfly 10
> * Teiid Server 9.2.3
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Attachments: image-2017-05-24-17-24-08-386.png, list-vdbs-result.json, server.log
>
>
> After several deploys/undeploys of several VDBs, no VDB is listed any longer on console (Deployed Virtual Databases), although VDBs are effectively deployed.
> On logs:
> 2017-05-24 16:17:49,223 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker2_async-teiid-threads2) TEIID40003 VDB NetSuiteMappingVDB.1 is set to ACTIVE
> 2017-05-24 16:17:49,271 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker0_async-teiid-threads0) TEIID40003 VDB CerillionVDB.1 is set to ACTIVE
> 2017-05-24 16:17:50,187 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker3_async-teiid-threads3) TEIID40003 VDB SalesForceVDB.1 is set to ACTIVE
> 2017-05-24 16:17:50,609 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker4_async-teiid-threads4) TEIID40003 VDB BillingVDB.1 is set to ACTIVE
> 2017-05-24 16:17:52,012 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker3_async-teiid-threads5) TEIID40003 VDB CustomerVDB.1 is set to ACTIVE
> 2017-05-24 16:18:26,238 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads1) TEIID40003 VDB NetSuiteVDB.1 is set to ACTIVE
> 2017-05-24 16:18:26,584 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads6) TEIID40003 VDB ReferenceDataVDB.1 is set to ACTIVE
> 2017-05-24 16:18:27,115 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads7) TEIID40003 VDB FinanceVDB.1 is set to ACTIVE
> On console.
> !image-2017-05-24-17-24-08-386.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (TEIID-4931) No Deployed Virtual Databases on console
by Pedro Inácio (JIRA)
[ https://issues.jboss.org/browse/TEIID-4931?page=com.atlassian.jira.plugin... ]
Pedro Inácio updated TEIID-4931:
--------------------------------
Description:
[^list-vdbs-result.json] After several deploys/undeploys of several VDBs, no VDB is listed any longer on console (Deployed Virtual Databases), although VDBs are effectively deployed.
On logs:
2017-05-24 16:17:49,223 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker2_async-teiid-threads2) TEIID40003 VDB NetSuiteMappingVDB.1 is set to ACTIVE
2017-05-24 16:17:49,271 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker0_async-teiid-threads0) TEIID40003 VDB CerillionVDB.1 is set to ACTIVE
2017-05-24 16:17:50,187 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker3_async-teiid-threads3) TEIID40003 VDB SalesForceVDB.1 is set to ACTIVE
2017-05-24 16:17:50,609 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker4_async-teiid-threads4) TEIID40003 VDB BillingVDB.1 is set to ACTIVE
2017-05-24 16:17:52,012 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker3_async-teiid-threads5) TEIID40003 VDB CustomerVDB.1 is set to ACTIVE
2017-05-24 16:18:26,238 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads1) TEIID40003 VDB NetSuiteVDB.1 is set to ACTIVE
2017-05-24 16:18:26,584 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads6) TEIID40003 VDB ReferenceDataVDB.1 is set to ACTIVE
2017-05-24 16:18:27,115 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads7) TEIID40003 VDB FinanceVDB.1 is set to ACTIVE
On console.
!image-2017-05-24-17-24-08-386.png|thumbnail!
was:
After several deploys/undeploys of several VDBs, no VDB is listed any longer on console (Deployed Virtual Databases), although VDBs are effectively deployed.
On logs:
2017-05-24 16:17:49,223 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker2_async-teiid-threads2) TEIID40003 VDB NetSuiteMappingVDB.1 is set to ACTIVE
2017-05-24 16:17:49,271 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker0_async-teiid-threads0) TEIID40003 VDB CerillionVDB.1 is set to ACTIVE
2017-05-24 16:17:50,187 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker3_async-teiid-threads3) TEIID40003 VDB SalesForceVDB.1 is set to ACTIVE
2017-05-24 16:17:50,609 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker4_async-teiid-threads4) TEIID40003 VDB BillingVDB.1 is set to ACTIVE
2017-05-24 16:17:52,012 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker3_async-teiid-threads5) TEIID40003 VDB CustomerVDB.1 is set to ACTIVE
2017-05-24 16:18:26,238 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads1) TEIID40003 VDB NetSuiteVDB.1 is set to ACTIVE
2017-05-24 16:18:26,584 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads6) TEIID40003 VDB ReferenceDataVDB.1 is set to ACTIVE
2017-05-24 16:18:27,115 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads7) TEIID40003 VDB FinanceVDB.1 is set to ACTIVE
On console.
!image-2017-05-24-17-24-08-386.png|thumbnail!
> No Deployed Virtual Databases on console
> ----------------------------------------
>
> Key: TEIID-4931
> URL: https://issues.jboss.org/browse/TEIID-4931
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.2.3
> Environment: * Wildfly 10
> * Teiid Server 9.2.3
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Attachments: image-2017-05-24-17-24-08-386.png, list-vdbs-result.json, server.log
>
>
> [^list-vdbs-result.json] After several deploys/undeploys of several VDBs, no VDB is listed any longer on console (Deployed Virtual Databases), although VDBs are effectively deployed.
> On logs:
> 2017-05-24 16:17:49,223 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker2_async-teiid-threads2) TEIID40003 VDB NetSuiteMappingVDB.1 is set to ACTIVE
> 2017-05-24 16:17:49,271 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker0_async-teiid-threads0) TEIID40003 VDB CerillionVDB.1 is set to ACTIVE
> 2017-05-24 16:17:50,187 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker3_async-teiid-threads3) TEIID40003 VDB SalesForceVDB.1 is set to ACTIVE
> 2017-05-24 16:17:50,609 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker4_async-teiid-threads4) TEIID40003 VDB BillingVDB.1 is set to ACTIVE
> 2017-05-24 16:17:52,012 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker3_async-teiid-threads5) TEIID40003 VDB CustomerVDB.1 is set to ACTIVE
> 2017-05-24 16:18:26,238 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads1) TEIID40003 VDB NetSuiteVDB.1 is set to ACTIVE
> 2017-05-24 16:18:26,584 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads6) TEIID40003 VDB ReferenceDataVDB.1 is set to ACTIVE
> 2017-05-24 16:18:27,115 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads7) TEIID40003 VDB FinanceVDB.1 is set to ACTIVE
> On console.
> !image-2017-05-24-17-24-08-386.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (TEIID-4931) No Deployed Virtual Databases on console
by Pedro Inácio (JIRA)
[ https://issues.jboss.org/browse/TEIID-4931?page=com.atlassian.jira.plugin... ]
Pedro Inácio commented on TEIID-4931:
-------------------------------------
Added the result of executing _/subsystem=teiid:list-vdbs()_
> No Deployed Virtual Databases on console
> ----------------------------------------
>
> Key: TEIID-4931
> URL: https://issues.jboss.org/browse/TEIID-4931
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.2.3
> Environment: * Wildfly 10
> * Teiid Server 9.2.3
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Attachments: image-2017-05-24-17-24-08-386.png, list-vdbs-result.json, server.log
>
>
> [^list-vdbs-result.json] After several deploys/undeploys of several VDBs, no VDB is listed any longer on console (Deployed Virtual Databases), although VDBs are effectively deployed.
> On logs:
> 2017-05-24 16:17:49,223 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker2_async-teiid-threads2) TEIID40003 VDB NetSuiteMappingVDB.1 is set to ACTIVE
> 2017-05-24 16:17:49,271 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker0_async-teiid-threads0) TEIID40003 VDB CerillionVDB.1 is set to ACTIVE
> 2017-05-24 16:17:50,187 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker3_async-teiid-threads3) TEIID40003 VDB SalesForceVDB.1 is set to ACTIVE
> 2017-05-24 16:17:50,609 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker4_async-teiid-threads4) TEIID40003 VDB BillingVDB.1 is set to ACTIVE
> 2017-05-24 16:17:52,012 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker3_async-teiid-threads5) TEIID40003 VDB CustomerVDB.1 is set to ACTIVE
> 2017-05-24 16:18:26,238 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads1) TEIID40003 VDB NetSuiteVDB.1 is set to ACTIVE
> 2017-05-24 16:18:26,584 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads6) TEIID40003 VDB ReferenceDataVDB.1 is set to ACTIVE
> 2017-05-24 16:18:27,115 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker1_async-teiid-threads7) TEIID40003 VDB FinanceVDB.1 is set to ACTIVE
> On console.
> !image-2017-05-24-17-24-08-386.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (TEIID-4928) Couchbase - NAMEINSOURCE required for all the columns and tables
by Juraj Duráni (JIRA)
[ https://issues.jboss.org/browse/TEIID-4928?page=com.atlassian.jira.plugin... ]
Juraj Duráni commented on TEIID-4928:
-------------------------------------
> Can you provide more details, like the exception, from a failing case?
There Is not exception. I received no result (not single row). With NAMEINSOURCE, I got correct result.
> Perhaps it would be possible to provide N1QL queries to pull a representative docs in addition to or instead of limit based sampling.
That would make more sense to me, but still there is a lot of catches for which defining metadata manually would be better (sparse data, not all possible attributes present in current documents, renaming, moving buckets...). So custom N1QL query is a good option, but I would not discourage user from defining metadata manually.
> ... for a column in teiid table to map to this kinds of attr in document, the NAMEINSOURCE is necessary.
I believe you have disproved this by yourself:
{quote}
teiid load metadata will create metadata aotomaticly, because each of columns represent a attr in a json document
{quote}
If Teiid is able to do mapping *JSON attribute --> Teiid column* during metadata loading without anything else, why it is not able to map it the other way round? I.e. *Teiid column --> JSON attribute*. In fact, during metadata load e.g. JSON attribute *myAttribute* is mapped to Teiid column *myAttribute*. Why Teiid cannot do the same while mapping Teiid column *myColumn* to attribute *myColumn*? I think, that Teiid should assume, that column name and attribute name is mapped 1-to-1 in both ways by default. Only if it is not true, then user needs to define NAMEINSOURCE.
> The table name map to keyspace name in couchbase...
This does not make sense to me. Why is table name mapped to keyspace and then there is *teiid_couchbase:NAMEDTYPEPAIR* which defines *attribute:table_name* pair? Moreover, keyspace is defined twice - first in resource-adapter definition, second in metadata. For me it would make more sense this:
# Define namespace and keyspace in resource-adapter definition
# For each table, define name of the attribute which determines table - e.g.:
{code:sql}
CREATE FOREIGN TABLE MyTable(....) OPTIONS ("teiid_couchbase:NAMEDTYPE" 'type')
{code}
# Now, N1QL could look like:
{code:sql}
SELECT ... FROM `<keyspace-from-resource-adapter>` `$cb_t1` LET ... WHERE `$cb_t1`.`<attribute-name-from-options>` = '<name-of-the-table>'
{code}
E.g.
{code:sql}
SELECT ... FROM `my_bucket` `$cb_t1` LET ... WHERE `$cb_t1`.`type` = 'MyTable'
{code}
> Another reason for a table need a NAMEINSOURCE is array table...
For array tables, I understand information like NAMEINSOURCE is needed and it could be tricky. But I wonder, whether we need to mess up NAMEINSOURCE and fact that table is array table.
Here is my suggestion (consider it really only suggestion as I did not try modeling them):
# Currently, there are two information that table is an array table - it is indicated by NAMEINSOURCE and teiid_couchbase:ISARRAYTABLE option.
# How about using only option
## change *teiid_couchbase:ISARRAYTABLE* to *teiid_couchbase:ARRAYTABLE*
## change type from boolean to string (with values like *nested\[\]\[\]*)
## if the option *IS NOT* present, consider table to be a regular table
## if the option *IS* present, consider table to be an array table and use value just like you use NAMEINSOURCE now
What do you think? Does it make sense?
> 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, 7 months