[JBoss JIRA] (TEIID-5072) Generated keys should be passed from triggers
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5072?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5072:
-------------------------------------
No problem, just trying to understand all options. What you proposed would be great.
> Generated keys should be passed from triggers
> ---------------------------------------------
>
> Key: TEIID-5072
> URL: https://issues.jboss.org/browse/TEIID-5072
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> In the context of an update trigger we should be able to convey the generated keys to the caller. In the case where only a single insert occurs, this should be automatic. Otherwise we'll need functions/variables to get/set the generated keys in the procedure. For example see the LAST_INSERT_ID function on mysql.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5074) Support a way provide SEQUENCE in TeiidDialect
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5074?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-5074:
--------------------------------
Description: Currently, the sequence based Table identity generation support is not available in current TeiidDialect. The support will not be direct, but with additional constructs in VDB, we can make this available. Teiid needs to provide a way to call in source specific (was: Currently, the sequence support is not available in current TeiidDialect. The support will not be direct, but with additional constructs in VDB, we can make this available. Proposal will be provided)
> Support a way provide SEQUENCE in TeiidDialect
> ----------------------------------------------
>
> Key: TEIID-5074
> URL: https://issues.jboss.org/browse/TEIID-5074
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Driver
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> Currently, the sequence based Table identity generation support is not available in current TeiidDialect. The support will not be direct, but with additional constructs in VDB, we can make this available. Teiid needs to provide a way to call in source specific
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5074) Support a way provide SEQUENCE in TeiidDialect
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5074?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-5074:
--------------------------------
Description: Currently, the sequence based Table identity generation support is not available in current TeiidDialect. The support will not be direct, but with additional constructs in VDB, we can make this available. Teiid needs to provide a way to call in source specific of way to insert a layer in Teiid to accomplish this. (was: Currently, the sequence based Table identity generation support is not available in current TeiidDialect. The support will not be direct, but with additional constructs in VDB, we can make this available. Teiid needs to provide a way to call in source specific)
> Support a way provide SEQUENCE in TeiidDialect
> ----------------------------------------------
>
> Key: TEIID-5074
> URL: https://issues.jboss.org/browse/TEIID-5074
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Driver
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> Currently, the sequence based Table identity generation support is not available in current TeiidDialect. The support will not be direct, but with additional constructs in VDB, we can make this available. Teiid needs to provide a way to call in source specific of way to insert a layer in Teiid to accomplish this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5074) Support a way provide SEQUENCE in TeiidDialect
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-5074:
-----------------------------------
Summary: Support a way provide SEQUENCE in TeiidDialect
Key: TEIID-5074
URL: https://issues.jboss.org/browse/TEIID-5074
Project: Teiid
Issue Type: Enhancement
Components: JDBC Driver
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 10.0
Currently, the sequence support is not available in current TeiidDialect. The support will not be direct, but with additional constructs in VDB, we can make this available. Proposal will be provided
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5071) Teiid designer Odata4 model import fails to load metadata and throws java.lang.NullPointerException
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-5071?page=com.atlassian.jira.plugin... ]
Debbie Steigner commented on TEIID-5071:
----------------------------------------
just an fyi, when I changed the translator on the source to odata instead of odata4, I get an unsupported operation error:
odata translator:
08:53:19,592 WARN [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50036 VDB importVDB1.1 model "importVDB1SrcModel" metadata failed to load. Reason:org.teiid.translator.TranslatorException: org.teiid.translator.TranslatorException
at org.teiid.translator.odata.ODataMetadataProcessor.getEds(ODataMetadataProcessor.java:113)
at org.teiid.translator.odata.ODataMetadataProcessor.process(ODataMetadataProcessor.java:118)
at org.teiid.translator.odata.ODataExecutionFactory.getMetadata(ODataExecutionFactory.java:123)
at org.teiid.translator.odata.ODataExecutionFactory.getMetadata(ODataExecutionFactory.java:64)
at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.UnsupportedOperationException
at org.odata4j.format.xml.EdmxFormatParser.parseMetadata(EdmxFormatParser.java:95)
at org.teiid.translator.odata.ODataMetadataProcessor.getEds(ODataMetadataProcessor.java:108)
... 12 more
> Teiid designer Odata4 model import fails to load metadata and throws java.lang.NullPointerException
> ---------------------------------------------------------------------------------------------------
>
> Key: TEIID-5071
> URL: https://issues.jboss.org/browse/TEIID-5071
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.12.6_3
> Reporter: Colin Mondesir
> Assignee: Steven Hawkins
>
> The odata4 translator throws a NPE when the designer attempts to import model.
> 08:55:36,424 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB importVDB1.1 model "importVDB1SrcModel" metadata failed to load. Reason:java.lang.NullPointerException: java.lang.NullPointerException
> at org.teiid.translator.odata4.ODataMetadataProcessor.addPrimaryKey(ODataMetadataProcessor.java:331)
> at org.teiid.translator.odata4.ODataMetadataProcessor.addEntityTypeProperties(ODataMetadataProcessor.java:243)
> at org.teiid.translator.odata4.ODataMetadataProcessor.addTable(ODataMetadataProcessor.java:219)
> at org.teiid.translator.odata4.ODataMetadataProcessor.getMetadata(ODataMetadataProcessor.java:122)
> at org.teiid.translator.odata4.ODataMetadataProcessor.process(ODataMetadataProcessor.java:105)
> at org.teiid.translator.odata4.ODataExecutionFactory.getMetadata(ODataExecutionFactory.java:119)
> at org.teiid.translator.odata4.ODataExecutionFactory.getMetadata(ODataExecutionFactory.java:69)
> at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5071) Teiid designer Odata4 model import fails to load metadata and throws java.lang.NullPointerException
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5071?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5071:
---------------------------------------
Logged as https://issues.apache.org/jira/browse/OLINGO-1186
> Teiid designer Odata4 model import fails to load metadata and throws java.lang.NullPointerException
> ---------------------------------------------------------------------------------------------------
>
> Key: TEIID-5071
> URL: https://issues.jboss.org/browse/TEIID-5071
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.12.6_3
> Reporter: Colin Mondesir
> Assignee: Steven Hawkins
>
> The odata4 translator throws a NPE when the designer attempts to import model.
> 08:55:36,424 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB importVDB1.1 model "importVDB1SrcModel" metadata failed to load. Reason:java.lang.NullPointerException: java.lang.NullPointerException
> at org.teiid.translator.odata4.ODataMetadataProcessor.addPrimaryKey(ODataMetadataProcessor.java:331)
> at org.teiid.translator.odata4.ODataMetadataProcessor.addEntityTypeProperties(ODataMetadataProcessor.java:243)
> at org.teiid.translator.odata4.ODataMetadataProcessor.addTable(ODataMetadataProcessor.java:219)
> at org.teiid.translator.odata4.ODataMetadataProcessor.getMetadata(ODataMetadataProcessor.java:122)
> at org.teiid.translator.odata4.ODataMetadataProcessor.process(ODataMetadataProcessor.java:105)
> at org.teiid.translator.odata4.ODataExecutionFactory.getMetadata(ODataExecutionFactory.java:119)
> at org.teiid.translator.odata4.ODataExecutionFactory.getMetadata(ODataExecutionFactory.java:69)
> at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5072) Generated keys should be passed from triggers
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5072?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-5072 at 9/21/17 11:03 AM:
-----------------------------------------------------------------
> Since you are saying the inherent case, how about the explicit trigger but single insert statement case?
That would still be built upon assumption unless we can do the appropriate analysis on the view definition. It also would require path analysis when branching statements are used. It's a lot of work for a corner case - and there's not a great way to convey to the user that the scenario won't work.
was (Author: shawkins):
> Since you are saying the inherent case, how about the explicit trigger but single insert statement case?
That would still be built upon assumption unless we can do the appropriate analysis on the view definition. It also would require path analysis when branching statements are used. It's a lot of work for a corner case.
> Generated keys should be passed from triggers
> ---------------------------------------------
>
> Key: TEIID-5072
> URL: https://issues.jboss.org/browse/TEIID-5072
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> In the context of an update trigger we should be able to convey the generated keys to the caller. In the case where only a single insert occurs, this should be automatic. Otherwise we'll need functions/variables to get/set the generated keys in the procedure. For example see the LAST_INSERT_ID function on mysql.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5072) Generated keys should be passed from triggers
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5072?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5072:
---------------------------------------
> Since you are saying the inherent case, how about the explicit trigger but single insert statement case?
That would still be built upon assumption unless we can do the appropriate analysis on the view definition. It also would require path analysis when branching statements are used. It's a lot of work for a corner case.
> Generated keys should be passed from triggers
> ---------------------------------------------
>
> Key: TEIID-5072
> URL: https://issues.jboss.org/browse/TEIID-5072
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> In the context of an update trigger we should be able to convey the generated keys to the caller. In the case where only a single insert occurs, this should be automatic. Otherwise we'll need functions/variables to get/set the generated keys in the procedure. For example see the LAST_INSERT_ID function on mysql.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5071) Teiid designer Odata4 model import fails to load metadata and throws java.lang.NullPointerException
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5071?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5071:
-------------------------------------
Ok, it is little confusing to me how they are using these both interfaces. Yes, looks like some consolidation is required. If you want open Olingo JIRA and I can assign to myself.
> Teiid designer Odata4 model import fails to load metadata and throws java.lang.NullPointerException
> ---------------------------------------------------------------------------------------------------
>
> Key: TEIID-5071
> URL: https://issues.jboss.org/browse/TEIID-5071
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.12.6_3
> Reporter: Colin Mondesir
> Assignee: Steven Hawkins
>
> The odata4 translator throws a NPE when the designer attempts to import model.
> 08:55:36,424 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB importVDB1.1 model "importVDB1SrcModel" metadata failed to load. Reason:java.lang.NullPointerException: java.lang.NullPointerException
> at org.teiid.translator.odata4.ODataMetadataProcessor.addPrimaryKey(ODataMetadataProcessor.java:331)
> at org.teiid.translator.odata4.ODataMetadataProcessor.addEntityTypeProperties(ODataMetadataProcessor.java:243)
> at org.teiid.translator.odata4.ODataMetadataProcessor.addTable(ODataMetadataProcessor.java:219)
> at org.teiid.translator.odata4.ODataMetadataProcessor.getMetadata(ODataMetadataProcessor.java:122)
> at org.teiid.translator.odata4.ODataMetadataProcessor.process(ODataMetadataProcessor.java:105)
> at org.teiid.translator.odata4.ODataExecutionFactory.getMetadata(ODataExecutionFactory.java:119)
> at org.teiid.translator.odata4.ODataExecutionFactory.getMetadata(ODataExecutionFactory.java:69)
> at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (TEIID-5071) Teiid designer Odata4 model import fails to load metadata and throws java.lang.NullPointerException
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5071?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5071:
---------------------------------------
We may be talking past each other. Yes there are properties already on the xml metadata for version - they are exposed on the DataServices interface. However from the XMLMetadata interface there is no way to get at that information. So either Olingo should expose that or they should throw their own exception when parsing metadata that is not compatible.
> Teiid designer Odata4 model import fails to load metadata and throws java.lang.NullPointerException
> ---------------------------------------------------------------------------------------------------
>
> Key: TEIID-5071
> URL: https://issues.jboss.org/browse/TEIID-5071
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.12.6_3
> Reporter: Colin Mondesir
> Assignee: Steven Hawkins
>
> The odata4 translator throws a NPE when the designer attempts to import model.
> 08:55:36,424 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB importVDB1.1 model "importVDB1SrcModel" metadata failed to load. Reason:java.lang.NullPointerException: java.lang.NullPointerException
> at org.teiid.translator.odata4.ODataMetadataProcessor.addPrimaryKey(ODataMetadataProcessor.java:331)
> at org.teiid.translator.odata4.ODataMetadataProcessor.addEntityTypeProperties(ODataMetadataProcessor.java:243)
> at org.teiid.translator.odata4.ODataMetadataProcessor.addTable(ODataMetadataProcessor.java:219)
> at org.teiid.translator.odata4.ODataMetadataProcessor.getMetadata(ODataMetadataProcessor.java:122)
> at org.teiid.translator.odata4.ODataMetadataProcessor.process(ODataMetadataProcessor.java:105)
> at org.teiid.translator.odata4.ODataExecutionFactory.getMetadata(ODataExecutionFactory.java:119)
> at org.teiid.translator.odata4.ODataExecutionFactory.getMetadata(ODataExecutionFactory.java:69)
> at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.10.6_3-redhat-2.jar:8.12.10.6_3-redhat-2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months