June 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5364) Modeshape jcr_reference function has wrong return type

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5364?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5364. ----------------------------------- Resolution: Done Updated the return type. > Modeshape jcr_reference function has wrong return type > ------------------------------------------------------ > > Key: TEIID-5364 > URL: https://issues.jboss.org/browse/TEIID-5364 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.0 > > > The pushdown function is marked as a boolean, rather than returning the expected type of string. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5365) Remove function model support entirely

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5365: ------------------------------------- Summary: Remove function model support entirely Key: TEIID-5365 URL: https://issues.jboss.org/browse/TEIID-5365 Project: Teiid Issue Type: Task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 11.0 Function model support has been deprecated for some time and should be completely removed from the server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5364) Modeshape jcr_reference function has wrong return type

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5364: ------------------------------------- Summary: Modeshape jcr_reference function has wrong return type Key: TEIID-5364 URL: https://issues.jboss.org/browse/TEIID-5364 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 11.0 The pushdown function is marked as a boolean, rather than returning the expected type of string. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5313) Oracle translator issue with mixing string types and general issues with non-ascii strings

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5313?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5313: --------------------------------- Fix Version/s: 8.12.14.6_4 > Oracle translator issue with mixing string types and general issues with non-ascii strings > ------------------------------------------------------------------------------------------ > > Key: TEIID-5313 > URL: https://issues.jboss.org/browse/TEIID-5313 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.3, 10.1.3, 10.2.1, 8.12.14.6_4 > > > Oracle produces an exception when internationalized and regular character strings are mixed via a union or case statement, for example: > case when val = 'x' then 'x' else N'y' end > The translator only puts the N literal prefix when a non-ascii character is present though. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5361) Column metadata with set queries only reflects projected branch

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5361?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5361. ----------------------------------- Resolution: Done Added logic around unions and literals - mostly for string and decimal types. > Column metadata with set queries only reflects projected branch > --------------------------------------------------------------- > > Key: TEIID-5361 > URL: https://issues.jboss.org/browse/TEIID-5361 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.0 > > > The logic in the MetaDataProcessor only considers the projected branch when determining attributes beyond type, thus it may not accurately represent the expected results. > We should also look at returning metadata that is more specific to literal values. For example: > select 'a' > would return the generic type metadata for 'a', rather than a more specific length. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5360) DatabaseMetaData nullsAreSortedLow should not be true

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5360?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5360: --------------------------------------- I'll try to drive this from the server as we've allowed the admin to configure the server side default for some time now. > DatabaseMetaData nullsAreSortedLow should not be true > ----------------------------------------------------- > > Key: TEIID-5360 > URL: https://issues.jboss.org/browse/TEIID-5360 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.0 > > > Since there isn't a hard guarantee of null sorts (without an explicit null sort) we should not indicate nulls are low in the DatabaseMetaData. This will leave all of the null sort methods as false, which may be an issue for some clients so a flag should be added to control this behavior. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5360) DatabaseMetaData nullsAreSortedLow should not be true

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5360?page=com.atlassian.jira.plugin... ] Work on TEIID-5360 started by Steven Hawkins. --------------------------------------------- > DatabaseMetaData nullsAreSortedLow should not be true > ----------------------------------------------------- > > Key: TEIID-5360 > URL: https://issues.jboss.org/browse/TEIID-5360 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.0 > > > Since there isn't a hard guarantee of null sorts (without an explicit null sort) we should not indicate nulls are low in the DatabaseMetaData. This will leave all of the null sort methods as false, which may be an issue for some clients so a flag should be added to control this behavior. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5363) SimpleDB connector not quoting table names in internal Select queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5363?page=com.atlassian.jira.plugin... ] Work on TEIID-5363 started by Steven Hawkins. --------------------------------------------- > SimpleDB connector not quoting table names in internal Select queries > --------------------------------------------------------------------- > > Key: TEIID-5363 > URL: https://issues.jboss.org/browse/TEIID-5363 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Pranav K > Assignee: Steven Hawkins > Fix For: 11.0, 10.3.2, 10.2.3 > > > Facing an issue while querying the Simple DB connector for a specific type of tables - the tables that contain a hyphen in the name. > According to the SimpleDB documentation: > Attribute and domain names may appear without quotes if they contain only letters, numbers, underscores (_), or dollar symbols ($) and do not start with a number. You must quote all other attribute and domain names with the backtick (`). > (https://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGuide/QuotingR...) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5363) SimpleDB connector not quoting table names in internal Select queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5363?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5363: ---------------------------------- Component/s: Misc. Connectors Fix Version/s: 11.0 10.3.2 10.2.3 > SimpleDB connector not quoting table names in internal Select queries > --------------------------------------------------------------------- > > Key: TEIID-5363 > URL: https://issues.jboss.org/browse/TEIID-5363 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Pranav K > Assignee: Steven Hawkins > Fix For: 11.0, 10.3.2, 10.2.3 > > > Facing an issue while querying the Simple DB connector for a specific type of tables - the tables that contain a hyphen in the name. > According to the SimpleDB documentation: > Attribute and domain names may appear without quotes if they contain only letters, numbers, underscores (_), or dollar symbols ($) and do not start with a number. You must quote all other attribute and domain names with the backtick (`). > (https://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGuide/QuotingR...) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5356) Infer field metadata from the source columns

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5356?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5356. ----------------------------------- Resolution: Done Added logic to the MetadataValidator.addColumn to consult the actual metadata object or defer to the MetaDataProcessor to determine better column metadata. This is not perfect, but with a couple of related fixes such as TEIID-5361 and TEIID-5359 it's much better than it was. > Infer field metadata from the source columns > -------------------------------------------- > > Key: TEIID-5356 > URL: https://issues.jboss.org/browse/TEIID-5356 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Fix For: 11.0 > > > This is an observation made in dynamic vdbs. > When a view is defined without column name , data type, length as in the example below > create view xyz as ( > select a, b, c from view_model.example > ); > instead of inferring the column metadata from view_model, the string columns are created with length =4000, this is causing issues when querying such views from visualization tools like Tableau, these fields are forced to be converted to text and failing in the process. > I would like to request an enhancement for dynamic vdbs to infer metadata from sources in such cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2018