January 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4719) Add a ddl equivalent to the metadata tag

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4719?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4719: ---------------------------------- Component/s: Query Engine To keep things similar to today that would be the easiest as the ddl, or whatever is scoped only to the given schema. So it could be generic as: IMPORT SCHEMA {name} FROM {repo} {arg} We just need to be clear on the semantics of import - that is the schema can already exist and we're adding to it. > Add a ddl equivalent to the metadata tag > ---------------------------------------- > > Key: TEIID-4719 > URL: https://issues.jboss.org/browse/TEIID-4719 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > Generally we'll need something that is equivalent to the metadata tag - that can specify a repo and options. In a zip deployment this will allow splitting the ddl over multiple files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4719) Add a ddl equivalent to the metadata tag

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4719?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-4719 at 1/24/17 7:14 PM: ---------------------------------------------------------------- To keep things similar to today that would be the easiest as the ddl, or whatever is scoped only to the given schema. So it could be generic as: {code} IMPORT SCHEMA {name} FROM {repo} {arg} {code} We just need to be clear on the semantics of import - that is the schema can already exist and we're adding to it. was (Author: shawkins): To keep things similar to today that would be the easiest as the ddl, or whatever is scoped only to the given schema. So it could be generic as: IMPORT SCHEMA {name} FROM {repo} {arg} We just need to be clear on the semantics of import - that is the schema can already exist and we're adding to it. > Add a ddl equivalent to the metadata tag > ---------------------------------------- > > Key: TEIID-4719 > URL: https://issues.jboss.org/browse/TEIID-4719 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > Generally we'll need something that is equivalent to the metadata tag - that can specify a repo and options. In a zip deployment this will allow splitting the ddl over multiple files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4629) Offer a ddl solution to replace the vdb.xml

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4629?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4629: --------------------------------------- You don't have to reference the current schema if there is one already - however what I'm saying is that create schema doesn't imply that the current schema is set. See the comment on TEIID-4536 You would need: create schema x ... use schema x; create view ...; and/or with TEIID-4536 create schema x ... as statements > Offer a ddl solution to replace the vdb.xml > ------------------------------------------- > > Key: TEIID-4629 > URL: https://issues.jboss.org/browse/TEIID-4629 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Based upon the work on TEIID-2578 we should first offer the ability to replace the vdb.xml with ddl. We can additionally include some of the work to represent additional pieces of the vdb as api level metadata objects (instead of in the admin layer) where possible. Ideally this should support as much alter functionality as possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4719) Add a ddl equivalent to the metadata tag

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4719?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4719: ------------------------------------- Can we do something like {code} IMPORT SCHEMA {name} FROM DDL-FILE {path} {code} instead of coming with whole different statement? we can also tie DDL-FILE semantic to any type MetadataRepository we may write in future? > Add a ddl equivalent to the metadata tag > ---------------------------------------- > > Key: TEIID-4719 > URL: https://issues.jboss.org/browse/TEIID-4719 > Project: Teiid > Issue Type: Sub-task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > Generally we'll need something that is equivalent to the metadata tag - that can specify a repo and options. In a zip deployment this will allow splitting the ddl over multiple files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4629) Offer a ddl solution to replace the vdb.xml

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4629?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4629: ------------------------------------- I thought at one in the beginning we did have the SET|USE SCHEMA statement, we later removed citing the context of the statement to assume the current SCHEMA. > Offer a ddl solution to replace the vdb.xml > ------------------------------------------- > > Key: TEIID-4629 > URL: https://issues.jboss.org/browse/TEIID-4629 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Based upon the work on TEIID-2578 we should first offer the ability to replace the vdb.xml with ddl. We can additionally include some of the work to represent additional pieces of the vdb as api level metadata objects (instead of in the admin layer) where possible. Ideally this should support as much alter functionality as possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4722) TEIID30019: java.lang.AssertionError: Assertion failed assertion due to guard against a corner condition.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4722?page=com.atlassian.jira.plugin... ] Work on TEIID-4722 started by Steven Hawkins. --------------------------------------------- > TEIID30019: java.lang.AssertionError: Assertion failed assertion due to guard against a corner condition. > ----------------------------------------------------------------------------------------------------------- > > Key: TEIID-4722 > URL: https://issues.jboss.org/browse/TEIID-4722 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.10.6_2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > > Assertion failure: > {code:java} > ERROR [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue19151) TEIID30019 Unexpected exception for request WrzxYIqVWQ8G.11: java.lang.AssertionError: Assertion failed. > at org.teiid.core.util.Assertion.failed(Assertion.java:73) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.core.util.Assertion.assertTrue(Assertion.java:68) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.core.util.Assertion.assertTrue(Assertion.java:60) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.MergeJoinStrategy.setProcessingSortRight(MergeJoinStrategy.java:367) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.DependentAccessNode.prepareNextCommand(DependentAccessNode.java:162) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.AccessNode.openInternal(AccessNode.java:259) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:371) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3624) No way to associate enterprise data types in dynamic vdb constructs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3624?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3624: ---------------------------------- Fix Version/s: 9.3 (was: 9.2) Moving to 9.3. The work in progress is at https://github.com/shawkins/teiid/commits/TEIID-3624 There is still quite a bit to be ironed out - such as if we are going to allow schema scoping, array base types, metadata reporting, and additional restrictions (such as making the names exception and serial reserved). > No way to associate enterprise data types in dynamic vdb constructs > ------------------------------------------------------------------- > > Key: TEIID-3624 > URL: https://issues.jboss.org/browse/TEIID-3624 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.3 > > > I don't find any doc's on how to define enterprise data types in a dynamic vdb. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4629) Offer a ddl solution to replace the vdb.xml

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4629?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-4629 at 1/24/17 6:08 PM: ---------------------------------------------------------------- Also typically create database/schema does not imply that you are connected to that database/schema and a use/set statement is still required. was (Author: shawkins): Also typically create database does not imply that you are connected to that database and a use statement is still required. > Offer a ddl solution to replace the vdb.xml > ------------------------------------------- > > Key: TEIID-4629 > URL: https://issues.jboss.org/browse/TEIID-4629 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Based upon the work on TEIID-2578 we should first offer the ability to replace the vdb.xml with ddl. We can additionally include some of the work to represent additional pieces of the vdb as api level metadata objects (instead of in the admin layer) where possible. Ideally this should support as much alter functionality as possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4720) changes in requiresLeftLinearJoin and useParensForJoins needed for Hive

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4720?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4720. ----------------------------------- Fix Version/s: 9.2 Resolution: Done Updated hive to be the same as impala - see also TEIID-3641 > changes in requiresLeftLinearJoin and useParensForJoins needed for Hive > ----------------------------------------------------------------------- > > Key: TEIID-4720 > URL: https://issues.jboss.org/browse/TEIID-4720 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.9.6_3 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 9.2 > > > 4 table join in Hive requires settings: > requiresLeftLinearJoin true, useParensForJoins false -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4722) TEIID30019: java.lang.AssertionError: Assertion failed assertion due to guard against a corner condition.

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4722?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4722: --------------------------------- Summary: TEIID30019: java.lang.AssertionError: Assertion failed assertion due to guard against a corner condition. (was: TEIID30019: java.lang.AssertionError: Assertion failed (summary wip)) > TEIID30019: java.lang.AssertionError: Assertion failed assertion due to guard against a corner condition. > ----------------------------------------------------------------------------------------------------------- > > Key: TEIID-4722 > URL: https://issues.jboss.org/browse/TEIID-4722 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.10.6_2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > > Assertion failure: > {code:java} > ERROR [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue19151) TEIID30019 Unexpected exception for request WrzxYIqVWQ8G.11: java.lang.AssertionError: Assertion failed. > at org.teiid.core.util.Assertion.failed(Assertion.java:73) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.core.util.Assertion.assertTrue(Assertion.java:68) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.core.util.Assertion.assertTrue(Assertion.java:60) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.MergeJoinStrategy.setProcessingSortRight(MergeJoinStrategy.java:367) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.DependentAccessNode.prepareNextCommand(DependentAccessNode.java:162) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.AccessNode.openInternal(AccessNode.java:259) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:371) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2017