April 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5726) java.lang.NullPointerException when calling a stored procedure via Teiid

by Christoph John (Jira)

[ https://issues.jboss.org/browse/TEIID-5726?page=com.atlassian.jira.plugin... ] Christoph John updated TEIID-5726: ---------------------------------- Issue Type: Bug (was: Enhancement) Priority: Blocker (was: Major) > java.lang.NullPointerException when calling a stored procedure via Teiid > ------------------------------------------------------------------------ > > Key: TEIID-5726 > URL: https://issues.jboss.org/browse/TEIID-5726 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 12.1 > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Blocker > Attachments: log3.txt, srcProc.txt, svc-vdb.ddl > > > I try to create a function import for a stored procedure which I have in my sql database. When executing the stored procedure via mysql workbench, the stored procedure does fine. > I have described the issue in my first message in > https://developer.jboss.org/message/989044#989044 > in detail. Attached you find the excerpt from the teiid error log and my vdb file. The relevant stored procedure is named srcProc and is also attached. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5726) java.lang.NullPointerException when calling a stored procedure via Teiid

by Christoph John (Jira)

Christoph John created TEIID-5726: ------------------------------------- Summary: java.lang.NullPointerException when calling a stored procedure via Teiid Key: TEIID-5726 URL: https://issues.jboss.org/browse/TEIID-5726 Project: Teiid Issue Type: Enhancement Components: OData Affects Versions: 12.1 Reporter: Christoph John Assignee: Steven Hawkins Attachments: log3.txt, srcProc.txt, svc-vdb.ddl I try to create a function import for a stored procedure which I have in my sql database. When executing the stored procedure via mysql workbench, the stored procedure does fine. I have described the issue in my first message in https://developer.jboss.org/message/989044#989044 in detail. Attached you find the excerpt from the teiid error log and my vdb file. The relevant stored procedure is named srcProc and is also attached. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5725) Please improve documentation on definition of stored procedures, virtual functions and virtual procedures

by Christoph John (Jira)

Christoph John created TEIID-5725: ------------------------------------- Summary: Please improve documentation on definition of stored procedures, virtual functions and virtual procedures Key: TEIID-5725 URL: https://issues.jboss.org/browse/TEIID-5725 Project: Teiid Issue Type: Enhancement Reporter: Christoph John Assignee: Steven Hawkins I refer to the discussion with Ramesh in https://developer.jboss.org/message/989048#989048 and would like to ask for a more detailed explanation on how to write virtual procedures and functions. -Especially, how are OUT and INOUT params set and how can they be obtained via odata. - How is the return value of a virtual function set? - How are collections and arrays of collections returned? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5724) Issues with Informix Date/Time types

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5724?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-5724 at 4/19/19 4:24 PM: ---------------------------------------------------------------- Corrected the type mappings and updated the calendar methods to either not use a calendar or to use a cloned one. The informix client will keep date/time/timestamp values consistent with respect to calendar fields for a given client timezone - that is regardless of what the client timezone is in, a value of 2000-01-01 01:01:01 will always be displayed in the local timezone. The database timezone property should only be set if that is not the desired behavior, and instead want the values adjusted to assume a fixed timezone. However as noted in the older issue the informix driver for some reason seems to adjust timestamps and time values in the opposite direction. With the Teiid server in GMT (or really any timezone) a given set of row values for a query are: Date 2000-02-19 Time 01:00:00 Timestamp 2000-01-01 00:00:49.0 With the client in GMT and the DatabaseTimezone set to GMT-1, you see: Date 2000-02-19 Time 00:00:00 Timestamp 2000-01-01 01:00:49.0 Note the time and timestamp moved in opposite directions. I did a second commit to account for this by switching to our logic for the adjustment. was (Author: shawkins): Corrected the type mappings and updated the calendar methods to either not use a calendar or to use a cloned one. The informix client will keep date/time/timestamp values consistent with respect to calendar fields for a given client timezone - that is regardless of what the client timezone is in, a value of 2000-01-01 01:01:01 will always be displayed in the local timezone. The database timezone property should only be set if that is not the desired behavior, and instead want the values adjusted to assume a fixed timezone. However as noted in the older issue the informix driver for some reason seems to adjust timestamps and time values in the opposite direction. With the Teiid server in GMT (or really any timezone) a given set of row values for a query are: Date 2000-02-19 Time 01:00:00 Timestamp 2000-01-01 00:00:49.0 With the client in GMT and the DatabaseTimezone set to GMT-1, you see: Date 2000-02-19 Time 00:00:00 Timestamp 2000-01-01 01:00:49.0 Note the time and timestamp moved in opposite directions. I did not yet try to account for this assuming for now that most will want the default behavior. > Issues with Informix Date/Time types > ------------------------------------ > > Key: TEIID-5724 > URL: https://issues.jboss.org/browse/TEIID-5724 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2, 11.2.3, 12.1.1 > > > Informix date/time issues include: > Timestamp/Time are mapped to the same conversion - datetime hour to second > The Timestamp mapping needs to be fully specified - datetime year to fraction(5), not just datetime > Usage of the getXXX Resultset methods passing a Calendar result in odd behavior as Informix modifies that Calendar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5724) Issues with Informix Date/Time types

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5724?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5724. ----------------------------------- Resolution: Done Corrected the type mappings and updated the calendar methods to either not use a calendar or to use a cloned one. The informix client will keep date/time/timestamp values consistent with respect to calendar fields for a given client timezone - that is regardless of what the client timezone is in, a value of 2000-01-01 01:01:01 will always be displayed in the local timezone. The database timezone property should only be set if that is not the desired behavior, and instead want the values adjusted to assume a fixed timezone. However as noted in the older issue the informix driver for some reason seems to adjust timestamps and time values in the opposite direction. With the Teiid server in GMT (or really any timezone) a given set of row values for a query are: Date 2000-02-19 Time 01:00:00 Timestamp 2000-01-01 00:00:49.0 With the client in GMT and the DatabaseTimezone set to GMT-1, you see: Date 2000-02-19 Time 00:00:00 Timestamp 2000-01-01 01:00:49.0 Note the time and timestamp moved in opposite directions. I did not yet try to account for this assuming for now that most will want the default behavior. > Issues with Informix Date/Time types > ------------------------------------ > > Key: TEIID-5724 > URL: https://issues.jboss.org/browse/TEIID-5724 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2, 11.2.3, 12.1.1 > > > Informix date/time issues include: > Timestamp/Time are mapped to the same conversion - datetime hour to second > The Timestamp mapping needs to be fully specified - datetime year to fraction(5), not just datetime > Usage of the getXXX Resultset methods passing a Calendar result in odd behavior as Informix modifies that Calendar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5724) Issues with Informix Date/Time types

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5724: ------------------------------------- Summary: Issues with Informix Date/Time types Key: TEIID-5724 URL: https://issues.jboss.org/browse/TEIID-5724 Project: Teiid Issue Type: Bug Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.2, 11.2.3, 12.1.1 Informix date/time issues include: Timestamp/Time are mapped to the same conversion - datetime hour to second The Timestamp mapping needs to be fully specified - datetime year to fraction(5), not just datetime Usage of the getXXX Resultset methods passing a Calendar result in odd behavior as Informix modifies that Calendar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-63) Support Keycloak based OpenID authentication for OData Through 3scale

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-63?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIIDSB-63: ----------------------------------- Assignee: Ramesh Reddy > Support Keycloak based OpenID authentication for OData Through 3scale > --------------------------------------------------------------------- > > Key: TEIIDSB-63 > URL: https://issues.jboss.org/browse/TEIIDSB-63 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Support the authentication for OData through 3scale -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-63) Support Keycloak based OpenID authentication for OData Through 3scale

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-63?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIIDSB-63: -------------------------------- Fix Version/s: 1.1.0 > Support Keycloak based OpenID authentication for OData Through 3scale > --------------------------------------------------------------------- > > Key: TEIIDSB-63 > URL: https://issues.jboss.org/browse/TEIIDSB-63 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Support the authentication for OData through 3scale -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-65) OData include files are not being served correctly

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-65?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-65: ------------------------------------- Yes, it will be same as /static usecase. > OData include files are not being served correctly > -------------------------------------------------- > > Key: TEIIDSB-65 > URL: https://issues.jboss.org/browse/TEIIDSB-65 > Project: Teiid Spring Boot > Issue Type: Bug > Components: OData > Affects Versions: 1.0.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 1.1.0 > > > The include metadata files are not being served correctly through OData interface. > One of the reference is calculated as http://rdbms-example-odata-teiid-dataservice.apps.garys-e21d.openshiftwor... > The class tries to request from this include url and this is what causes the 406 error > see $metadata int he URL -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-63) Support Keycloak based OpenID authentication for OData Through 3scale

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-63?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-63: ------------------------------------- A good article to configure RH-SSO with 3scale https://developers.redhat.com/blog/2017/11/21/setup-3scale-openid-connect... > Support Keycloak based OpenID authentication for OData Through 3scale > --------------------------------------------------------------------- > > Key: TEIIDSB-63 > URL: https://issues.jboss.org/browse/TEIIDSB-63 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Ramesh Reddy > Priority: Major > > Support the authentication for OData through 3scale -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2019