May 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4908) Access Pattern Messaging

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIID-4908?page=com.atlassian.jira.plugin... ] Steve Tran updated TEIID-4908: ------------------------------ > Access Pattern Messaging > ------------------------ > > Key: TEIID-4908 > URL: https://issues.jboss.org/browse/TEIID-4908 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.8.6_3 > Environment: JDV 6.3.2 > Windows 7 > Reporter: Steve Tran > Assignee: Johnathon Lee > > I'm accessing my JDV table via OData4 through Salesforce's UI builder. The salesforce engine itself is creating the OData calls, and whenever a $filter is needed with multiple columns, it looks like salesforce pads the column name with a space in front and behind. That'll make the URL look like ...$filter={color:red}%20{color}ColumnA{color:red}%20{color}eq%20123%20and{color:red}%20{color}ColumnB{color:red}%20{color}eq... > The first space right after the $filter= throws off the JDV engine as it thinks it's a malformed URL - which I guess it is. The thing is when I tested it via the OData2 interface, it accepted it just fine. I'm not sure if the OData4 specifications explicitly state in terms of the URL, so it could be anybody's bug. Perhaps we could make JDV a little more forgiving and trim the spaces after un-URL-encoding the URI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4908) Access Pattern Messaging

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIID-4908?page=com.atlassian.jira.plugin... ] Steve Tran updated TEIID-4908: ------------------------------ Fix Version/s: (was: 8.12.x-6.4) (was: 8.12.11.6_3) > Access Pattern Messaging > ------------------------ > > Key: TEIID-4908 > URL: https://issues.jboss.org/browse/TEIID-4908 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.8.6_3 > Environment: JDV 6.3.2 > Windows 7 > Reporter: Steve Tran > Assignee: Johnathon Lee > > I'm accessing my JDV table via OData4 through Salesforce's UI builder. The salesforce engine itself is creating the OData calls, and whenever a $filter is needed with multiple columns, it looks like salesforce pads the column name with a space in front and behind. That'll make the URL look like ...$filter={color:red}%20{color}ColumnA{color:red}%20{color}eq%20123%20and{color:red}%20{color}ColumnB{color:red}%20{color}eq... > The first space right after the $filter= throws off the JDV engine as it thinks it's a malformed URL - which I guess it is. The thing is when I tested it via the OData2 interface, it accepted it just fine. I'm not sure if the OData4 specifications explicitly state in terms of the URL, so it could be anybody's bug. Perhaps we could make JDV a little more forgiving and trim the spaces after un-URL-encoding the URI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4908) Access Pattern Messaging

by Steve Tran (JIRA)

Steve Tran created TEIID-4908: --------------------------------- Summary: Access Pattern Messaging Key: TEIID-4908 URL: https://issues.jboss.org/browse/TEIID-4908 Project: Teiid Issue Type: Bug Components: OData Affects Versions: 8.12.8.6_3 Environment: JDV 6.3.2 Windows 7 Reporter: Steve Tran Assignee: Johnathon Lee Fix For: 8.12.x-6.4, 8.12.11.6_3 I'm accessing my JDV table via OData4 through Salesforce's UI builder. The salesforce engine itself is creating the OData calls, and whenever a $filter is needed with multiple columns, it looks like salesforce pads the column name with a space in front and behind. That'll make the URL look like ...$filter={color:red}%20{color}ColumnA{color:red}%20{color}eq%20123%20and{color:red}%20{color}ColumnB{color:red}%20{color}eq... The first space right after the $filter= throws off the JDV engine as it thinks it's a malformed URL - which I guess it is. The thing is when I tested it via the OData2 interface, it accepted it just fine. I'm not sure if the OData4 specifications explicitly state in terms of the URL, so it could be anybody's bug. Perhaps we could make JDV a little more forgiving and trim the spaces after un-URL-encoding the URI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4907) Sybase and other import should tolerate exception retrieving foreign keys

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4907: ------------------------------------- Summary: Sybase and other import should tolerate exception retrieving foreign keys Key: TEIID-4907 URL: https://issues.jboss.org/browse/TEIID-4907 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.3 Sybase throws an exception when asking for foreign key information on a view - this can be prevented by checking the table type. In general we should tolerate an exception when asking for the foreign keys. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4905) Verify and Provide .NET connectivity

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4905?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4905: ------------------------------------- Fix Version/s: Open To Community 10.x Assignee: (was: Steven Hawkins) > Verify and Provide .NET connectivity > ------------------------------------ > > Key: TEIID-4905 > URL: https://issues.jboss.org/browse/TEIID-4905 > Project: Teiid > Issue Type: Feature Request > Components: Common > Reporter: Ramesh Reddy > Fix For: Open To Community, 10.x > > > The user should be able to connect to Teiid using .NET libraries. Postgres supports [1], this should be verified. > [1] http://www.npgsql.org/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3360) Provide an option to virtualize source exceptions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3360?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3360: ------------------------------------- Fix Version/s: 10.x (was: 9.3) Assignee: (was: Steven Hawkins) > Provide an option to virtualize source exceptions > ------------------------------------------------- > > Key: TEIID-3360 > URL: https://issues.jboss.org/browse/TEIID-3360 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Fix For: 10.x > > > Currently we'll pass the source exception along with the Teiid exception. And from source sql exceptions we'll also rely the sql state/code. When connecting to databases of different types it would be best to return a common set of codes. > There is exception mapping logic in Hibernate that we could reuse, but this could apply to the non-jdbc sources such that a predictable code will seen by Teiid clients. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4857) Add file metadata such as creation and last modified date to file translator functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4857?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4857: --------------------------------------- Can we get a clarification on the design - is the metadata supposed to follow the clob/blob and then some other function will ask for it? Or can there be other procedure(s) on the file translator to return the metadata given the path? The former is more difficult to ensure as there isn't a proper notion of file blob/clob - most operations on the value, for example inlining, will make it loose the original reference that is held by the fileinputstreamfactory. > Add file metadata such as creation and last modified date to file translator functions > -------------------------------------------------------------------------------------- > > Key: TEIID-4857 > URL: https://issues.jboss.org/browse/TEIID-4857 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Add file metadata such as creation date and last modified date to the data returned by the file translator functions (getFiles/getTextFiles). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4906) Clean up licensing and copyright information

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4906?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4906. ----------------------------------- Resolution: Done Also updated the saxon xom logic to what is found in the saxon source to consolidate on an MPL 2 license. Unfortunately saxon does not provide the classes in binary form, so we will still need to look at creating a separate module. > Clean up licensing and copyright information > -------------------------------------------- > > Key: TEIID-4906 > URL: https://issues.jboss.org/browse/TEIID-4906 > Project: Teiid > Issue Type: Sub-task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3 > > > There is some drift in our copyright and licensing information. We also need to more broadly advertise the ancillary licenses we are pulling in. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4906) Clean up licensing and copyright information

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4906?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4906: --------------------------------------- Initial clean up in 9.3 - remove epl code from StringUtil, so now it is just lgpl - relicense the metadata module under EPL. The module is now under both the lgpl and epl - we could simplify this to just epl. - as explained in the readme update where applicable the poms were updated with additional license information, a specific copyright file was added, etc. > Clean up licensing and copyright information > -------------------------------------------- > > Key: TEIID-4906 > URL: https://issues.jboss.org/browse/TEIID-4906 > Project: Teiid > Issue Type: Sub-task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3 > > > There is some drift in our copyright and licensing information. We also need to more broadly advertise the ancillary licenses we are pulling in. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4474) Re-license under a more permissive license

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4474?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4474: --------------------------------------- We need to separate our MPL (saxon related) code into a new module for this. > Re-license under a more permissive license > ------------------------------------------ > > Key: TEIID-4474 > URL: https://issues.jboss.org/browse/TEIID-4474 > Project: Teiid > Issue Type: Task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > There has been some interest in Teiid re-licensing with a more permissive license, such as the ASL or MIT license. Beyond the obvious work of altering headers and license files, we need permission from the original copyright/copyleft holders to approve the change. > We'd likely want to use the ASL, but if there are any concerns about GPL compatibility we'll consider the MIT license. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 May 2017