November 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3112) Incorrect plural name with parent to child join

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-3112?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIID-3112: -------------------------------- Comment: was deleted (was: [~mmakovy] Matus, can you attach the dynamic VDB xml file that works? ) > Incorrect plural name with parent to child join > ----------------------------------------------- > > Key: TEIID-3112 > URL: https://issues.jboss.org/browse/TEIID-3112 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9, 8.7.2, 8.7.1.6_2 > > > The salesforce logic assumes the plural name can be created with just an 's' at the end, however objects such as Opportunity do not follow that pattern. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3112) Incorrect plural name with parent to child join

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-3112?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-3112: ------------------------------------- [~mmakovy] Matus, can you attach the dynamic VDB xml file that works? > Incorrect plural name with parent to child join > ----------------------------------------------- > > Key: TEIID-3112 > URL: https://issues.jboss.org/browse/TEIID-3112 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9, 8.7.2, 8.7.1.6_2 > > > The salesforce logic assumes the plural name can be created with just an 's' at the end, however objects such as Opportunity do not follow that pattern. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3758) Allow for a 2048 bit DH key exchange

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3758?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3758. ----------------------------------- Resolution: Done Added a 2048 bit key exchange when supported by both the client and server - it's known that 1.7 oracle/sun JREs don't support 2048 bit keys. Also updated/expanded the docs. > Allow for a 2048 bit DH key exchange > ------------------------------------ > > Key: TEIID-3758 > URL: https://issues.jboss.org/browse/TEIID-3758 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There's a general recommendation to migrate to longer dh key lengths - https://weakdh.org/imperfect-forward-secrecy-ccs15.pdf -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3758) Allow for a 2048 bit DH key exchange

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3758?page=com.atlassian.jira.plugin... ] Work on TEIID-3758 started by Steven Hawkins. --------------------------------------------- > Allow for a 2048 bit DH key exchange > ------------------------------------ > > Key: TEIID-3758 > URL: https://issues.jboss.org/browse/TEIID-3758 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There's a general recommendation to migrate to longer dh key lengths - https://weakdh.org/imperfect-forward-secrecy-ccs15.pdf -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3750) Allow the parsing of an expression

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3750?page=com.atlassian.jira.plugin... ] Work on TEIID-3750 started by Steven Hawkins. --------------------------------------------- > Allow the parsing of an expression > ---------------------------------- > > Key: TEIID-3750 > URL: https://issues.jboss.org/browse/TEIID-3750 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > Now that we have an extension property, we could allow an expression to be used in parsing rather than just a string. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3793) Push Teiid function LOCATE() to SQL Server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3793?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3793. ----------------------------------- Resolution: Done Added support to SQL Server, but not to sybase as it supports only the two argument form. > Push Teiid function LOCATE() to SQL Server > ------------------------------------------ > > Key: TEIID-3793 > URL: https://issues.jboss.org/browse/TEIID-3793 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Affects Versions: 8.7.1.6_2 > Environment: JBOSS DV 6.2 > Microsoft SQL Server 10.50.1600.1 > Reporter: Jean-Pierre Matsumoto > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.2 > > > We have some Teiid views with query similar to: > SELECT col1 > FROM tableA > WHERE SUBSTRING(col1, 1, LOCATE(' ', col1)) = 'PREFIX' > SQL Server receives a full scan of col1 table without WHERE: > SELECT col1 > FROM tableA > Because Teiid LOCATE() function is not translated to CHARINDEX() SQL Server function (SUBSTRING is translated). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3750) Allow the parsing of an expression

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3750?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3750: ---------------------------------- Fix Version/s: 9.0 (was: 8.12.2) Moving to a feature release as there isn't a specific driver for 8.12.x. > Allow the parsing of an expression > ---------------------------------- > > Key: TEIID-3750 > URL: https://issues.jboss.org/browse/TEIID-3750 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > Now that we have an extension property, we could allow an expression to be used in parsing rather than just a string. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3787) ignored properties in dynamic vdb should be flagged with a WARN log entry

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3787?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3787: ---------------------------------- Fix Version/s: 8.13 > ignored properties in dynamic vdb should be flagged with a WARN log entry > ------------------------------------------------------------------------- > > Key: TEIID-3787 > URL: https://issues.jboss.org/browse/TEIID-3787 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.7.1.6_2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.2 > > > Invalid properties are silently ignored, this can be troublesome to diagnose when there is a case mismatch, etc. useConnectorMetadata vs. UseConnectorMetadata > {code:java} > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <vdb name="test" version="1"> > <property name="useConnectorMetadata" value="true"/> > <property name="BREAK ME" value="true"/> > > <model name="EMPTY"> > > </model> > </vdb> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3787) ignored properties in dynamic vdb should be flagged with a WARN log entry

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3787?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3787. ----------------------------------- Fix Version/s: 8.12.2 Resolution: Done Added a detail logging specifically for what metadata caching value is used. > ignored properties in dynamic vdb should be flagged with a WARN log entry > ------------------------------------------------------------------------- > > Key: TEIID-3787 > URL: https://issues.jboss.org/browse/TEIID-3787 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.7.1.6_2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.12.2 > > > Invalid properties are silently ignored, this can be troublesome to diagnose when there is a case mismatch, etc. useConnectorMetadata vs. UseConnectorMetadata > {code:java} > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <vdb name="test" version="1"> > <property name="useConnectorMetadata" value="true"/> > <property name="BREAK ME" value="true"/> > > <model name="EMPTY"> > > </model> > </vdb> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3798) response code for "primary key of parent table not found"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3798?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3798. ----------------------------------- Resolution: Rejected The current behavior is appears to be spec compliant. > response code for "primary key of parent table not found" > --------------------------------------------------------- > > Key: TEIID-3798 > URL: https://issues.jboss.org/browse/TEIID-3798 > Project: Teiid > Issue Type: Bug > Reporter: Prashanthi Kairuppala > Assignee: Steven Hawkins > Priority: Critical > > Hi, > > When the primary key of the parent table is not found in the below kind of odata URL: > > odata/VDB/ParentTable/123/ChildTable > > then the response code is expected to be 404/500 or any error code, but we are getting 200 OK success code. > > Thanks, > Prashanthi. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2015