June 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4309) loadMatView getting the row count may not be correct

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4309: ------------------------------------- Summary: loadMatView getting the row count may not be correct Key: TEIID-4309 URL: https://issues.jboss.org/browse/TEIID-4309 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.11 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1 For an explicit load the row count is obtained by a query against the materialization table prior to the after load script, but there is no requirement that the materialization table or the metadata declared staging table represents the next state. We should move the row count call to after the "after load" or even make it optional. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4306) xa datasource create cli not work due to datasource change in wildfly 10

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4306?page=com.atlassian.jira.plugin... ] Kylin Soong updated TEIID-4306: ------------------------------- Fix Version/s: 9.1 > xa datasource create cli not work due to datasource change in wildfly 10 > ------------------------------------------------------------------------ > > Key: TEIID-4306 > URL: https://issues.jboss.org/browse/TEIID-4306 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Affects Versions: 9.1 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.1 > > > Due to the change of datasource in wildfly 10, create xa datasource cli like > {code} > /subsystem=datasources/xa-data-source=oracleXADS:add(jndi-name="${db.jndi_name}", driver-name=oracleXA, user-name="${db.user}", password="${db.password}", use-java-context=true) > {code} > It throw the following error > {code} > { > "outcome" => "failed", > "failure-description" => "WFLYJCA0069: At least one xa-datasource-property is required for an xa-datasource", > "rolled-back" => true > } > {code} > This affects to the following cli scripts: > * db2/create-db2-xa-ds.cli > * mysql/create-mysql-xa-ds.cli > * oracle/create-oracle-xa-ds.cli > * postgresql/create-postgresql-xa-ds.cli > * sqlserver/native/create-ms-native-xa-ds.cli > * sqlserver/jtds/create-jtds-xa-ds.cli > * teiid/create-teiid-xa-ds.cli -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4228) ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIID-4228?page=com.atlassian.jira.plugin... ] Steve Tran commented on TEIID-4228: ----------------------------------- I think we only need a validation warning/error message because once identified, it's not hard to fix in the VDB metadata via Teiid Designer. Like you said, this only affects one usage scenario (SQL Server) that we know of so far. > ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns > ----------------------------------------------------------------------------------- > > Key: TEIID-4228 > URL: https://issues.jboss.org/browse/TEIID-4228 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7 > Environment: Connections through ODBC driver > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.x > > > Connections through ODBC driver with the driver setting "Parse Statements" option enabled can result in incorrect length values being passed to the client. In some cases (such as SQL Server linked server capabilities), this can result in the client throwing exceptions due to the expected LENGTH changing during the course of the query execution. > This may be limited to columns with precision set to 0, as the SQL Server linked server case was corrected when the precision was changed from 0 to 9 for the column specified in the error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4230) Add more examples to demonstrates integrate hadoop ecosystem product and socialmedia to teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4230?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4230: ---------------------------------- Component/s: Documentation Fix Version/s: 9.1 (was: 9.x) > Add more examples to demonstrates integrate hadoop ecosystem product and socialmedia to teiid > --------------------------------------------------------------------------------------------- > > Key: TEIID-4230 > URL: https://issues.jboss.org/browse/TEIID-4230 > Project: Teiid > Issue Type: Task > Components: Documentation > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: JieRen JieRen > Fix For: 9.1 > > > Add more examples to demonstrates integrate Big Data(hadoop ecosystem products) and Social Media with teiid. > ||Name||Type||Description||Status|| > |sqoop integration |Big Data |use Apache Sqoop(http://sqoop.apache.org/) transfer data in embedded-portfolio(https://github.com/teiid/teiid-embedded-examples/tree/...'s Stock to Apache Hadoop; and transfer data from Apache Hadoop into Teiid VDB. | Scheduled | > |spark integration |Big Data | Apache spark(http://spark.apache.org/) can both consume JDBC source and provide JDBC interface for integrated by others, add example to demonstrate this |Scheduled | > |impala integration|Big Data | add a example to demonstrate impala translator and integrate impala with Teiid. | Scheduled | > |weibo integration|Social Media|Use Weibo api(http://open.weibo.com/wiki/API%E6%96%87%E6%A1%A3_V2/en) can get feeds as json, use ws translator/connector to convert return json to relational models | Scheduled | -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4228) ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4228?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4228: --------------------------------------- On the Teiid side there are a couple of considerations: Do we add a validation warning/error when the precision is non-positive on a numeric type? And/or do we add a workaround specifically for the odbc layer Since this only affects one odbc usage scenario and only for a regression in metadata load, I don't want to over do this on the Teiid side. > ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns > ----------------------------------------------------------------------------------- > > Key: TEIID-4228 > URL: https://issues.jboss.org/browse/TEIID-4228 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7 > Environment: Connections through ODBC driver > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.x > > > Connections through ODBC driver with the driver setting "Parse Statements" option enabled can result in incorrect length values being passed to the client. In some cases (such as SQL Server linked server capabilities), this can result in the client throwing exceptions due to the expected LENGTH changing during the course of the query execution. > This may be limited to columns with precision set to 0, as the SQL Server linked server case was corrected when the precision was changed from 0 to 9 for the column specified in the error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4228) ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-4228?page=com.atlassian.jira.plugin... ] Debbie Steigner edited comment on TEIID-4228 at 6/29/16 3:21 PM: ----------------------------------------------------------------- I tested with an old Teiid Designer (9.0.1) and a Microsoft SQL Server column with numeric(9,2) imports with precision of 9 and scale of 2, but in 9.0.7 and 10.0 beta precision is 0, scale is still 2. Looks like for other reasons the default precision of bigdecimal was changed to 0 in 9.0.5 Teiid Designer - https://issues.jboss.org/browse/TEIIDDES-2746 but that is if it isn't specified and it is on the MSSQL side. I logged a Designer bug for this https://issues.jboss.org/browse/TEIIDDES-2865 was (Author: dsteigne): I tested with an old Teiid Designer (9.0.1) and a Microsoft SQL Server column with numeric(9,2) imports with precision of 9 and scale of 2, but in 9.0.7 and 10.0 beta precision is 0, scale is still 2. Looks like for other reasons the default precision of bigdecimal was changed to 0 in 9.0.5 Teiid Designer - https://issues.jboss.org/browse/TEIIDDES-2746 but that is if it isn't specified and it is on the MSSQL side. I log a Designer bug for this https://issues.jboss.org/browse/TEIIDDES-2865 > ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns > ----------------------------------------------------------------------------------- > > Key: TEIID-4228 > URL: https://issues.jboss.org/browse/TEIID-4228 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7 > Environment: Connections through ODBC driver > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.x > > > Connections through ODBC driver with the driver setting "Parse Statements" option enabled can result in incorrect length values being passed to the client. In some cases (such as SQL Server linked server capabilities), this can result in the client throwing exceptions due to the expected LENGTH changing during the course of the query execution. > This may be limited to columns with precision set to 0, as the SQL Server linked server case was corrected when the precision was changed from 0 to 9 for the column specified in the error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4228) ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-4228?page=com.atlassian.jira.plugin... ] Debbie Steigner edited comment on TEIID-4228 at 6/29/16 3:20 PM: ----------------------------------------------------------------- I tested with an old Teiid Designer (9.0.1) and a Microsoft SQL Server column with numeric(9,2) imports with precision of 9 and scale of 2, but in 9.0.7 and 10.0 beta precision is 0, scale is still 2. Looks like for other reasons the default precision of bigdecimal was changed to 0 in 9.0.5 Teiid Designer - https://issues.jboss.org/browse/TEIIDDES-2746 but that is if it isn't specified and it is on the MSSQL side. I log a Designer bug for this https://issues.jboss.org/browse/TEIIDDES-2865 was (Author: dsteigne): I tested with an old Teiid Designer (9.0.1) and a Microsoft SQL Server column with numeric(9,2) imports with precision of 9 and scale of 2, but in 9.0.7 and 10.0 beta precision is 0, scale is still 2. Looks like for other reasons the default precision of bigdecimal was changed to 0 in 9.0.5 Teiid Designer - https://issues.jboss.org/browse/TEIIDDES-2746 but that is if it isn't specified and it is on the MSSQL side. I'll log a Designer bug on this. > ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns > ----------------------------------------------------------------------------------- > > Key: TEIID-4228 > URL: https://issues.jboss.org/browse/TEIID-4228 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7 > Environment: Connections through ODBC driver > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.x > > > Connections through ODBC driver with the driver setting "Parse Statements" option enabled can result in incorrect length values being passed to the client. In some cases (such as SQL Server linked server capabilities), this can result in the client throwing exceptions due to the expected LENGTH changing during the course of the query execution. > This may be limited to columns with precision set to 0, as the SQL Server linked server case was corrected when the precision was changed from 0 to 9 for the column specified in the error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4228) ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-4228?page=com.atlassian.jira.plugin... ] Debbie Steigner commented on TEIID-4228: ---------------------------------------- I tested with an old Teiid Designer (9.0.1) and a Microsoft SQL Server column with numeric(9,2) imports with precision of 9 and scale of 2, but in 9.0.7 and 10.0 beta precision is 0, scale is still 2. Looks like for other reasons the default precision of bigdecimal was changed to 0 in 9.0.5 Teiid Designer - https://issues.jboss.org/browse/TEIIDDES-2746 but that is if it isn't specified and it is on the MSSQL side. I'll log a Designer bug on this. > ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns > ----------------------------------------------------------------------------------- > > Key: TEIID-4228 > URL: https://issues.jboss.org/browse/TEIID-4228 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7 > Environment: Connections through ODBC driver > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.x > > > Connections through ODBC driver with the driver setting "Parse Statements" option enabled can result in incorrect length values being passed to the client. In some cases (such as SQL Server linked server capabilities), this can result in the client throwing exceptions due to the expected LENGTH changing during the course of the query execution. > This may be limited to columns with precision set to 0, as the SQL Server linked server case was corrected when the precision was changed from 0 to 9 for the column specified in the error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4247) OData - support date and time functions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4247?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4247: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1351328|https://bugzilla.redhat.com/show_bug.cgi?id=1351328] from NEW to ASSIGNED > OData - support date and time functions > --------------------------------------- > > Key: TEIID-4247 > URL: https://issues.jboss.org/browse/TEIID-4247 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > Fix For: 9.1 > > > The functions date() and time() are currently not supported in odata queries, e.g. running query {noformat}http://localhost:8080/odata4/olingo_basic/Source/SimpleDataTable?$filter=timeval%20gt%20time(now()){noformat} > returns {code:xml} > <?xml version='1.0' encoding='UTF-8'?> > <error xmlns="http://docs.oasis-open.org/odata/ns/metadata"> > <code>TEIID16027</code> > <message>TEIID16027 Function time is not currently supported </message> > </error> > {code} > This is allowed behaviour per the [odata spec|http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/par...], but it would be good to have these functions implemented. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4247) OData - support date and time functions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4247?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4247: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1351328 Bugzilla Update: Perform > OData - support date and time functions > --------------------------------------- > > Key: TEIID-4247 > URL: https://issues.jboss.org/browse/TEIID-4247 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > Fix For: 9.1 > > > The functions date() and time() are currently not supported in odata queries, e.g. running query {noformat}http://localhost:8080/odata4/olingo_basic/Source/SimpleDataTable?$filter=timeval%20gt%20time(now()){noformat} > returns {code:xml} > <?xml version='1.0' encoding='UTF-8'?> > <error xmlns="http://docs.oasis-open.org/odata/ns/metadata"> > <code>TEIID16027</code> > <message>TEIID16027 Function time is not currently supported </message> > </error> > {code} > This is allowed behaviour per the [odata spec|http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/par...], but it would be good to have these functions implemented. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 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 2016