January 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4700) Google translator inconsistent behavior for DELETE and SELECT for null values

by Lucie Fabrikova (JIRA)

Lucie Fabrikova created TEIID-4700: -------------------------------------- Summary: Google translator inconsistent behavior for DELETE and SELECT for null values Key: TEIID-4700 URL: https://issues.jboss.org/browse/TEIID-4700 Project: Teiid Issue Type: Bug Affects Versions: 9.2 Environment: 9.2.0.Alpha2 Reporter: Lucie Fabrikova Assignee: Steven Hawkins In teiid I observed following inconsistent behavior: Q1: select intnum, intkey from smalla where intnum > -10 AND intnum < 20 Q2: delete from smalla where intnum > -10 AND intnum < 20 Q1 returns rows without null values for intnum, but Q2 deletes also rows with null values for intnum. I observed that if I remove the lower boundary (ie. Q3: select intnum, intkey from smalla where intnum < 20 and similarly for delete), both returned and deleted rows contain null values, so the result is consistent. The server.log is empty, so I didn't attach it... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4699) Summary of PrestoDB translator function issues

by Kylin Soong (JIRA)

Kylin Soong created TEIID-4699: ---------------------------------- Summary: Summary of PrestoDB translator function issues Key: TEIID-4699 URL: https://issues.jboss.org/browse/TEIID-4699 Project: Teiid Issue Type: Task Components: Misc. Connectors Affects Versions: 9.2.1 Reporter: Kylin Soong Assignee: Kylin Soong Fix For: 9.2.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4630) Polish the teiid rest generated war

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4630?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-4630: ------------------------------------ I have done a quick evaluation, there need some UI design work, i have tested the rough design, it looks more ugly than current BASIC mode. I set to resolve, if necessary, we can open the issue in future. > Polish the teiid rest generated war > ------------------------------------ > > Key: TEIID-4630 > URL: https://issues.jboss.org/browse/TEIID-4630 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.2 > > Attachments: rest-screen.png > > > I have 2 aspect thoughts to beautify the rest war login/doc page: > * Change the login type from default BASIC to Client-Login, which like Dashbuilder, once request > {note} > http://{HOST}:{PORT}/{VDB_BANE}_{VDB_VERSION}/api > {note} > first will redirect to client login page, rather than pop up a small rough login window. > * Add a top green bar and log(as discussed in TEIIDDES-3006) to api doc page -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4630) Polish the teiid rest generated war

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4630?page=com.atlassian.jira.plugin... ] Kylin Soong resolved TEIID-4630. -------------------------------- Resolution: Done > Polish the teiid rest generated war > ------------------------------------ > > Key: TEIID-4630 > URL: https://issues.jboss.org/browse/TEIID-4630 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.2 > > Attachments: rest-screen.png > > > I have 2 aspect thoughts to beautify the rest war login/doc page: > * Change the login type from default BASIC to Client-Login, which like Dashbuilder, once request > {note} > http://{HOST}:{PORT}/{VDB_BANE}_{VDB_VERSION}/api > {note} > first will redirect to client login page, rather than pop up a small rough login window. > * Add a top green bar and log(as discussed in TEIIDDES-3006) to api doc page -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4698) Adding an INFO validation to a model can invalidate the vdb

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4698: ------------------------------------- Summary: Adding an INFO validation to a model can invalidate the vdb Key: TEIID-4698 URL: https://issues.jboss.org/browse/TEIID-4698 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.2, 9.1.3 See the forum link for a full detail of a vdb that is being reloaded while an info validation is left on a model. The xml we are generating is not valid for parsing again because no info enum is listed in the xsd. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4696) Teiid datasource driver does not reconnect after socket is closed

by Rafael Coutinho (JIRA)

[ https://issues.jboss.org/browse/TEIID-4696?page=com.atlassian.jira.plugin... ] Rafael Coutinho closed TEIID-4696. ---------------------------------- Great converting the datasource to the below it fixed it: {code:java} <datasource jndi-name="java:/ldapDS" pool-name="rhLdapDS" enabled="true"> <connection-url>jdbc:teiid:ldapVDB@mms://jdv.qa.a1.vary.redhat.com:31000;version=1</connection-url> <driver>teiid-8.13.3-jdbc.jar</driver> <pool> <prefill>false</prefill> <use-strict-min>false</use-strict-min> <flush-strategy>FailingConnectionOnly</flush-strategy> </pool> <security> <user-name>--</user-name> <password>**</password> </security> </datasource> {code} > Teiid datasource driver does not reconnect after socket is closed > ----------------------------------------------------------------- > > Key: TEIID-4696 > URL: https://issues.jboss.org/browse/TEIID-4696 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.13.3 > Environment: - Red Hat JBoss Enterprise Application Platform - Version 6.4.5.GA > - Load Balancer > - Red Hat JBoss Data Virtualization - Version 6.3.0 > Reporter: Rafael Coutinho > Assignee: Steven Hawkins > Attachments: one_first_exceptions.txt, two_repeated_exceptions.txt > > > Our setup has a JBoss app server with a datasource configured to query a virtual database deployend on a JDV server that is behind a load balancer. > The load balancer drops any connection after 10 minutes. For some reason the datasource client driver does not fix the connection when the socket gets closed. So in any queries done after the socket is closed are breaking, they log that the socket is closed but it never re establishes the connection again. > Attachment one has the first exception stack trace, attachment number two has the subsequent ones. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4697) Swagger translator issue with content type charsets

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4697: ------------------------------------- Summary: Swagger translator issue with content type charsets Key: TEIID-4697 URL: https://issues.jboss.org/browse/TEIID-4697 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Kylin Soong Fix For: 9.2.1 >From https://github.com/teiid/teiid/issues/858 - the logic needs to better handle when a charset is specified with the content type. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4696) Teiid datasource driver does not reconnect after socket is closed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4696?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4696. ----------------------------------- Resolution: Rejected A socket being closed will nominally terminate the connection. Use the autoFailover connection property if you want the connection to restablish in the event of a transport level error. > Teiid datasource driver does not reconnect after socket is closed > ----------------------------------------------------------------- > > Key: TEIID-4696 > URL: https://issues.jboss.org/browse/TEIID-4696 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.13.3 > Environment: - Red Hat JBoss Enterprise Application Platform - Version 6.4.5.GA > - Load Balancer > - Red Hat JBoss Data Virtualization - Version 6.3.0 > Reporter: Rafael Coutinho > Assignee: Steven Hawkins > Attachments: one_first_exceptions.txt, two_repeated_exceptions.txt > > > Our setup has a JBoss app server with a datasource configured to query a virtual database deployend on a JDV server that is behind a load balancer. > The load balancer drops any connection after 10 minutes. For some reason the datasource client driver does not fix the connection when the socket gets closed. So in any queries done after the socket is closed are breaking, they log that the socket is closed but it never re establishes the connection again. > Attachment one has the first exception stack trace, attachment number two has the subsequent ones. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4696) Teiid datasource driver does not reconnect after socket is closed

by Rafael Coutinho (JIRA)

Rafael Coutinho created TEIID-4696: -------------------------------------- Summary: Teiid datasource driver does not reconnect after socket is closed Key: TEIID-4696 URL: https://issues.jboss.org/browse/TEIID-4696 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 8.13.3 Environment: - Red Hat JBoss Enterprise Application Platform - Version 6.4.5.GA - Load Balancer - Red Hat JBoss Data Virtualization - Version 6.3.0 Reporter: Rafael Coutinho Assignee: Steven Hawkins Attachments: one_first_exceptions.txt, two_repeated_exceptions.txt Our setup has a JBoss app server with a datasource configured to query a virtual database deployend on a JDV server that is behind a load balancer. The load balancer drops any connection after 10 minutes. For some reason the datasource client driver does not fix the connection when the socket gets closed. So in any queries done after the socket is closed are breaking, they log that the socket is closed but it never re establishes the connection again. Attachment one has the first exception stack trace, attachment number two has the subsequent ones. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 commented on TEIID-3624: --------------------------------------- To further this discussion, we have to be clear on what the enterprise/udt feature is. I would like this to be driven first from a metadata perspective. Then we can decide what if any enhancement we work into the runtime side - such as being able to use field accessors complex.field, rather than a json/xml/array extraction function. We need to decide if the feature will be tied to the xsd type model - the initial indication from Barry is no. What features will we support for simple type faceting? What features will we support for complex types - and how will that relate to each complex base type geometry, json, xml? > 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.2 > > > 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)

9 years, 2 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 January 2017