September 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-118) zero precision loaded for java.sql.Timestamp

by Renat Eskenin (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-118?page=com.atlassian.jira.plugi... ] Renat Eskenin updated TEIIDSB-118: ---------------------------------- Steps to Reproduce: Teiid-spring-boot read metadata with several steps 0. (SystemMetadata.java:60) Teiid read metadata of datatypes from teiid-engine-12.3.0.jar/org/teiid/metadata/types.dat in this step teiid read wrong default precision (in file we have wrong value) for timestamp type (readed 0). (1 bug) 1. (JDBCMetadataProcessor.java:524) Teiid read metadata from JDBC and get precision in timestamp field as length of string with time (26) instead of get real precision (6). Real precision will write to scale (string 525) in column object. (2 bug) 2. In next step Teiid write DDL and read this DDL in parser (QueryParser:532) in this step we get precision as 0 and buggy precision = 26 will not using at all from previous step. (3 bug) 3. (ODataSchemaBuilder.java:556) In next step because precision for timestamp field is 0, Teeid set precision to 4 as default value (WHY! is 6 always 6 :)) 4. (EdmDateTimeOffset:164) So Apache Olingo4 rise exception because precision = 4 and value of nanos is xxxxxx000 where x is non zero time value and precision<count of x. I temporary fix this bugs by change default precision in teiid-engine-12.3.0.jar/org/teiid/metadata/types.dat to 6 for timestamp But need to full fix this issue. Thanks. was: Teiid-spring-boot read metadata with several steps 0. (SystemMetadata.java:60) Teiid read metadata of datatypes from teiid-engine-12.3.0.jar/org/teiid/metadata/types.dat in this step teiid read wrong default precision for timestamp type (readed 0). (1 bug) 1. (JDBCMetadataProcessor.java:524) Teiid read metadata from JDBC and get precision in timestamp field as length of string with time (26) instead of get real precision (6). Real precision will write to scale (string 525) in column object. (2 bug) 2. In next step Teiid write DDL and read this DDL in parser (QueryParser:532) in this step we get precision as 0 and buggy precision = 26 will not using at all from previous step. (3 bug) 3. (ODataSchemaBuilder.java:556) In next step because precision for timestamp field is 0, Teeid set precision to 4 as default value (WHY! is 6 always 6 :)) 4. (EdmDateTimeOffset:164) So Apache Olingo4 rise exception because precision = 4 and value of nanos is xxxxxx000 where x is non zero time value and precision<count of x. I temporary fix this bugs by change default precision in teiid-engine-12.3.0.jar/org/teiid/metadata/types.dat to 6 for timestamp But need to full fix this issue. Thanks. > zero precision loaded for java.sql.Timestamp > -------------------------------------------- > > Key: TEIIDSB-118 > URL: https://issues.jboss.org/browse/TEIIDSB-118 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource, OData > Affects Versions: 1.2.0 > Reporter: Renat Eskenin > Priority: Major > Attachments: image-2019-09-20-13-30-58-536.png, image-2019-09-20-13-34-56-255.png > > > I create spring-boot project for translate jdbc connection from vertica JDBC to odata4 REST interface. > When i get request to object with field witch Timestamp type i get the exception: > Request: > GET /vertica-odata-facade/odata/vertica/domain?%24top=1 > Response: > { > "error": { > "code": null, > "message": "The value '2019-09-12 09:26:22.323764' is not valid for property 'created_date'." > } > } > This field in vertica > !image-2019-09-20-13-34-56-255.png|thumbnail! > name: created_by_id > type: Timestamp > column size: 26 > decimal digits: 6 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-118) zero precision loaded for java.sql.Timestamp

by Renat Eskenin (Jira)

Renat Eskenin created TEIIDSB-118: ------------------------------------- Summary: zero precision loaded for java.sql.Timestamp Key: TEIIDSB-118 URL: https://issues.jboss.org/browse/TEIIDSB-118 Project: Teiid Spring Boot Issue Type: Bug Components: datasource, OData Affects Versions: 1.2.0 Reporter: Renat Eskenin Attachments: image-2019-09-20-13-30-58-536.png, image-2019-09-20-13-34-56-255.png I create spring-boot project for translate jdbc connection from vertica JDBC to odata4 REST interface. When i get request to object with field witch Timestamp type i get the exception: Request: GET /vertica-odata-facade/odata/vertica/domain?%24top=1 Response: { "error": { "code": null, "message": "The value '2019-09-12 09:26:22.323764' is not valid for property 'created_date'." } } This field in vertica !image-2019-09-20-13-34-56-255.png|thumbnail! name: created_by_id type: Timestamp column size: 26 decimal digits: 6 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-114) Validate vdb-import

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-114?page=com.atlassian.jira.plugi... ] Work on TEIIDSB-114 started by Ramesh Reddy. -------------------------------------------- > Validate vdb-import > ------------------- > > Key: TEIIDSB-114 > URL: https://issues.jboss.org/browse/TEIIDSB-114 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.2.0 > > > VDB Import should be supported through the Teiid Spring Boot. The groundwork has been done in the VDB plugin. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4866) Enhance SQL Alchemy integration to work with Superset

by Kolmar Vasconcelos (Jira)

[ https://issues.jboss.org/browse/TEIID-4866?page=com.atlassian.jira.plugin... ] Kolmar Vasconcelos commented on TEIID-4866: ------------------------------------------- Actually upgrading is not an option for me as I'm consuming TEIID as a service. I had worked around this with a SQLAlchemy dialect for TEIID. I will leave this here as a reference for users running on old versions of TEIID: https://github.com/kafran/sqlalchemy-teiid > Enhance SQL Alchemy integration to work with Superset > ----------------------------------------------------- > > Key: TEIID-4866 > URL: https://issues.jboss.org/browse/TEIID-4866 > Project: Teiid > Issue Type: Sub-task > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 9.3, 8.12.11.6_4 > > > Superset (previously Caravel) integration allows for an expanded set of sources, which was requested https://github.com/airbnb/superset/issues/241 > After some initial testing it looks like we still have some type and other issues to address. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4866) Enhance SQL Alchemy integration to work with Superset

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-4866?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4866: ------------------------------------- Much of work done in later versions, so we suggest upgrading to latest versions for this feature. > Enhance SQL Alchemy integration to work with Superset > ----------------------------------------------------- > > Key: TEIID-4866 > URL: https://issues.jboss.org/browse/TEIID-4866 > Project: Teiid > Issue Type: Sub-task > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 9.3, 8.12.11.6_4 > > > Superset (previously Caravel) integration allows for an expanded set of sources, which was requested https://github.com/airbnb/superset/issues/241 > After some initial testing it looks like we still have some type and other issues to address. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5815) Reduce the verbose metadata on Salesforce models

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5815?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5815. --------------------------------- Resolution: Done Added "includeExtensionMetadata` as importer property to control the metadata. > Reduce the verbose metadata on Salesforce models > ------------------------------------------------ > > Key: TEIID-5815 > URL: https://issues.jboss.org/browse/TEIID-5815 > Project: Teiid > Issue Type: Enhancement > Components: Salesforce Connector > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.3 > > > There are lot of metadata properties on the Salesforce models that are like > {code} > teiid_sf:Calculated" 'false', > teiid_sf:Custom" 'false', > teiid_sf:Defaulted on Create" 'true' > {code} > that are defined on the model, however they are never used by the engine to further process the queries. Thus these are effectively more of annotations then processing instructions for Teiid engine. These in some situations exceeding the limits of the metadata repository. > Provide an option to not include these in metadata based on a flag -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5815) Reduce the verbose metadata on Salesforce models

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5815: ----------------------------------- Summary: Reduce the verbose metadata on Salesforce models Key: TEIID-5815 URL: https://issues.jboss.org/browse/TEIID-5815 Project: Teiid Issue Type: Enhancement Components: Salesforce Connector Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 12.3 There are lot of metadata properties on the Salesforce models that are like {code} teiid_sf:Calculated" 'false', teiid_sf:Custom" 'false', teiid_sf:Defaulted on Create" 'true' {code} that are defined on the model, however they are never used by the engine to further process the queries. Thus these are effectively more of annotations then processing instructions for Teiid engine. These in some situations exceeding the limits of the metadata repository. Provide an option to not include these in metadata based on a flag -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4866) Enhance SQL Alchemy integration to work with Superset

by Kolmar Vasconcelos (Jira)

[ https://issues.jboss.org/browse/TEIID-4866?page=com.atlassian.jira.plugin... ] Kolmar Vasconcelos commented on TEIID-4866: ------------------------------------------- Is there a way to connect SQL Alchemy to TEIID version 8.12.13.6_3-redhat-1?? > Enhance SQL Alchemy integration to work with Superset > ----------------------------------------------------- > > Key: TEIID-4866 > URL: https://issues.jboss.org/browse/TEIID-4866 > Project: Teiid > Issue Type: Sub-task > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 9.3, 8.12.11.6_4 > > > Superset (previously Caravel) integration allows for an expanded set of sources, which was requested https://github.com/airbnb/superset/issues/241 > After some initial testing it looks like we still have some type and other issues to address. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5812) Associate Teiid validation errors with their run time objects for discoverability

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5812?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5812. ----------------------------------- Resolution: Done Updated the validation logic to set the path using just the fqn name segment - as we're already scoped to a schema. > Associate Teiid validation errors with their run time objects for discoverability > ---------------------------------------------------------------------------------- > > Key: TEIID-5812 > URL: https://issues.jboss.org/browse/TEIID-5812 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > The validation errors that are found during the deployment of VDB are currently associated with the Model/Schema object, where they kind of lose the identity of which schema item they belong to. > It would be good to associate with their respective runtime objects so that they can be easily discoverable -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5814) Add an async vdb loading mode to Teiid

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5814?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5814. ----------------------------------- Fix Version/s: 12.3 Resolution: Done Refactored the async logic into the common runtime. It will not be used by default with embedded - it needs the async-load vdb property set. We'll leave that as an undocumented option for now. > Add an async vdb loading mode to Teiid > -------------------------------------- > > Key: TEIID-5814 > URL: https://issues.jboss.org/browse/TEIID-5814 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > To support syndesis usage of embedded, we should have a the multi-threaded metadata load logic moved into a more common place so that not every vdb deployment is blocking. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2019