[JBoss JIRA] (TEIID-5106) Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid.
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5106?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5106:
----------------------------------
Issue Type: Quality Risk (was: Bug)
Priority: Major (was: Blocker)
This is unfortunately expected behavior. The only near term solution would be to offer an auto rename option that is similar to renameDuplicateColumns - TEIID-5046
> Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid.
> ----------------…
[View More]----------------------------------------------------------
>
> Key: TEIID-5106
> URL: https://issues.jboss.org/browse/TEIID-5106
> Project: Teiid
> Issue Type: Quality Risk
> Components: JDBC Connector
> Reporter: sameer P
> Assignee: Steven Hawkins
>
> In Postgres/Oracle/MS , I can create two tables with the same name (but different cases): test12 and Test12 (by quoting it in create script) , but, Teiid complains saying duplicate table name and fails with the below error:
> {code:java}
> 16:53:11,161 WARN [org.teiid.RUNTIME] (Worker0_async-teiid-threads0) TEIID50036 VDB test.1 model "dsms" metadata failed to load. Reason:TEIID60013 Duplicate Table public.test12: org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table public.test12
> at org.teiid.metadata.Schema.addTable(Schema.java:51)
> at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:179)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:351)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:324)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:166)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69)
> at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96)
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62)
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> at org.teiid.jboss.VDBService$6.run(VDBService.java:341)
> at org.teiid.jboss.VDBService$7.run(VDBService.java:392)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years, 6 months
[JBoss JIRA] (TEIID-5106) Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid.
by sameer P (JIRA)
sameer P created TEIID-5106:
-------------------------------
Summary: Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid.
Key: TEIID-5106
URL: https://issues.jboss.org/browse/TEIID-5106
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Reporter: sameer P
Assignee: Steven Hawkins
Priority: Blocker
In Postgres/Oracle/MS , I can create two tables …
[View More]with the same name (but different cases): test12 and Test12 (by quoting it in create script) , but, Teiid complains saying duplicate table name and fails with the below error:
{code:java}
16:53:11,161 WARN [org.teiid.RUNTIME] (Worker0_async-teiid-threads0) TEIID50036 VDB test.1 model "dsms" metadata failed to load. Reason:TEIID60013 Duplicate Table public.test12: org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table public.test12
at org.teiid.metadata.Schema.addTable(Schema.java:51)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:179)
at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368)
at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:351)
at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:324)
at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:166)
at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306)
at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69)
at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96)
at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62)
at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
at org.teiid.jboss.VDBService$6.run(VDBService.java:341)
at org.teiid.jboss.VDBService$7.run(VDBService.java:392)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years, 6 months
[JBoss JIRA] (TEIID-4854) Google translator fails to update timestamp value reformatted after update
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4854?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4854.
-----------------------------------
Resolution: Done
Added an import property to the google spreadsheet translator that disables automatically marking problematic types as updatable - allTypesUpdatable defaults to true for backwards compatibility, but setting to false will disable marking date/time/timestamp/numeric columns as updatable.
> Google translator fails to …
[View More]update timestamp value reformatted after update
> --------------------------------------------------------------------------
>
> Key: TEIID-4854
> URL: https://issues.jboss.org/browse/TEIID-4854
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.3, 8.12.10.6_3
> Reporter: Lucie Fabrikova
> Assignee: Steven Hawkins
> Fix For: 10.0
>
> Attachments: gs-reformatted-timestamp.log
>
>
> Cell of type timestamp is reformatted after an update. Data inserted from teiid are in format "yyyy-mm-dd hh:mm:ss[.fffffffff]", which is reformatted to "dd/mm/yyyy hh:mm:ss[.fffffffff]". Subsequent update of such row throws exception "Could not convert source column Source.smalla.timestampvalue to the expected runtime type timestamp".
> Google spreadsheet locale was UK, timezone was set to Berlin.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years, 6 months
[JBoss JIRA] (TEIID-4750) Map to BigInteger in more circumstances
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4750?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4750.
-----------------------------------
Resolution: Done
Promoted the oracle useIntegralTypes property to the general JDBC import logic. It will still default to false however.
> Map to BigInteger in more circumstances
> ---------------------------------------
>
> Key: TEIID-4750
> URL: https://issues.jboss.org/browse/TEIID-4750…
[View More]
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> We currently default to a bigdecimal mapping when a more specific biginteger mapping could be used. I think the original intent was to lessen our usage of the biginteger type as it's effectively derived from bigdecimal, but because of the weakness in the handling of precision/scale as the types propagate, biginteger can be more appropriate.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years, 6 months
[JBoss JIRA] (TEIID-5101) .vdb with JDG data source, with NATIVE defined, throws exception
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5101?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5101:
-------------------------------------
Yes, you can mix and match the models that we supported, but one model two different metadata types I am not sure that works. It not about generating the DDL, having that tag reads the metadata from Infinispan's .proto file to amend the defined DDL such that right data types, extension properties etc are generated by the metadata …
[View More]processor.
I am sure we can add in way to define "index" metadata and then also other types, but this requires changes in the Teiid Server, I am not sure it is worth the time as there is a good workaround and we want to retire the .vdb file.
> .vdb with JDG data source, with NATIVE defined, throws exception
> ----------------------------------------------------------------
>
> Key: TEIID-5101
> URL: https://issues.jboss.org/browse/TEIID-5101
> Project: Teiid
> Issue Type: Bug
> Components: Infinispan
> Affects Versions: 8.12.x-6.4
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Blocker
>
> When a .vdb (created in designer), and the internal vdb.xml contains the <metadata type="NATIVE"></metadata>, the vdb will not deploy.
> However, it will work if the .vdb is exported to vdb xml, because the DDL and the NATIVE tags are there.
> Guessing that the translator doesn't know how to handle a .vdb file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
7 years, 6 months