April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2922) Extra unique constraint in dynamic vdb schema

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2922?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2922: ------------------------------------- I guess as workaround user could turn off the importing of the keys in tooling meanwhile? > Extra unique constraint in dynamic vdb schema > --------------------------------------------- > > Key: TEIID-2922 > URL: https://issues.jboss.org/browse/TEIID-2922 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Steven Hawkins > > I'm getting an extra Unique Constraint in the dynamic VDB schema - for a MySQL table with only a primary key. See steps to reproduce. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2922) Extra unique constraint in dynamic vdb schema

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIID-2922?page=com.atlassian.jira.plugin... ] Mark Drilling commented on TEIID-2922: -------------------------------------- Ok, I didnt realize that. It does have a negative effect in the tooling tho. Import will result in a couple validation errors - 1) same named siblings and 2) PK and UC reference the same columns. Not sure how we're going to handle ATM > Extra unique constraint in dynamic vdb schema > --------------------------------------------- > > Key: TEIID-2922 > URL: https://issues.jboss.org/browse/TEIID-2922 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Steven Hawkins > > I'm getting an extra Unique Constraint in the dynamic VDB schema - for a MySQL table with only a primary key. See steps to reproduce. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2922) Extra unique constraint in dynamic vdb schema

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2922?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2922: --------------------------------------- Some databases report primary keys both as a key and as a unique constraint, so it does have two entries when we ask for get keys. Beyond clutter though, this doesn't have any negative effect - other than rippling the same double entry through our metadata. > Extra unique constraint in dynamic vdb schema > --------------------------------------------- > > Key: TEIID-2922 > URL: https://issues.jboss.org/browse/TEIID-2922 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Steven Hawkins > > I'm getting an extra Unique Constraint in the dynamic VDB schema - for a MySQL table with only a primary key. See steps to reproduce. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2922) Extra unique constraint in dynamic vdb schema

by Mark Drilling (JIRA)

Mark Drilling created TEIID-2922: ------------------------------------ Summary: Extra unique constraint in dynamic vdb schema Key: TEIID-2922 URL: https://issues.jboss.org/browse/TEIID-2922 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 8.4 Reporter: Mark Drilling Assignee: Steven Hawkins I'm getting an extra Unique Constraint in the dynamic VDB schema - for a MySQL table with only a primary key. See steps to reproduce. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2921) Allow the projection raising (or order pushing) logic to work with non-simple ordering expressions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2921?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2921: ---------------------------------- Fix Version/s: 8.8 > Allow the projection raising (or order pushing) logic to work with non-simple ordering expressions > -------------------------------------------------------------------------------------------------- > > Key: TEIID-2921 > URL: https://issues.jboss.org/browse/TEIID-2921 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.7.8 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.8 > > > Current logic is written to only support simple ordering expressions. User desires the ability to use non-simple Order By statements (for example: including a case statement) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2816) HBase Connector/Translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2816?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2816: ------------------------------------- Apache Phoenix Site http://phoenix.incubator.apache.org/ > HBase Connector/Translator > -------------------------- > > Key: TEIID-2816 > URL: https://issues.jboss.org/browse/TEIID-2816 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Connector, JDBC Driver > Affects Versions: Open To Community > Reporter: devin pinkston > Labels: HBase, Translator > > Develop a HBase translator/connector. Potentially using the Phoenix JDBC driver, supports most SQL and handles connections: > https://github.com/forcedotcom/phoenix -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2921) Allow the projection raising (or order pushing) logic to work with non-simple ordering expressions

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-2921: ------------------------------------ Summary: Allow the projection raising (or order pushing) logic to work with non-simple ordering expressions Key: TEIID-2921 URL: https://issues.jboss.org/browse/TEIID-2921 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.7.8 Reporter: Johnathon Lee Assignee: Steven Hawkins Current logic is written to only support simple ordering expressions. User desires the ability to use non-simple Order By statements (for example: including a case statement) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2712) AdminAPI getDataSourceNames is returning the pool name instead of jndi name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2712?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2712: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1023216|https://bugzilla.redhat.com/show_bug.cgi?id=1023216] from ASSIGNED to MODIFIED > AdminAPI getDataSourceNames is returning the pool name instead of jndi name > --------------------------------------------------------------------------- > > Key: TEIID-2712 > URL: https://issues.jboss.org/browse/TEIID-2712 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.6 > > > See related designer jira. The api call is returning the pool names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2877) Add support for MariaDB as a data source

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2877?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2877: -------------------------------- Fix Version/s: 8.7.1 (was: Open To Community) > Add support for MariaDB as a data source > ---------------------------------------- > > Key: TEIID-2877 > URL: https://issues.jboss.org/browse/TEIID-2877 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Van Halbert > Fix For: 8.7.1 > > > Red Hat will be making MariaDB its default DBMS in its next major Red Hat Enterprise Linux (RHEL) release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2920) Certain Translator Override Definitions for JDBC have identical display names

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2920?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2920. --------------------------------- Resolution: Done added as {code} @Deprecated @TranslatorProperty(display="Deprecated Property:Direct Query Procedure Name", description="Deprecated Property, use Direct Query Procedure Name", advanced=true) final public String getNativeQueryProcedureName() { return this.nativeProcedureName; } @TranslatorProperty(display="Deprecated Property:Supports Direct Query Procedure", description="Deprecated Property, Use Supports Direct Query Procedure instead", advanced=true) final public boolean supportsNativeQueries() { return this.supportsNativeQueries; } {code} > Certain Translator Override Definitions for JDBC have identical display names > ----------------------------------------------------------------------------- > > Key: TEIID-2920 > URL: https://issues.jboss.org/browse/TEIID-2920 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Ramesh Reddy > Fix For: 8.7 > > > In VDB editor, noticed that their are duplicate display names for certain JDBC translator properties. Confusing... > Debugged a little and here are the culprits I found: > ID = supportsDirectQueryProcedure > * Display Name = *Supports direct query procedure* > ID = supportsNativeQueries > * Display Name = *Supports direct query procedure* > ID = DirectQueryProcedureName > * Display Name = *Name of the direct query procedure* > ID = NativeQueryProcedureName > * Display Name = *Name of the direct query procedure* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2014