July 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4974) Couchbase - TRANSLATE function is transalted as REPLACE

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4974?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4974. ----------------------------------- Resolution: Done > Couchbase - TRANSLATE function is transalted as REPLACE > ------------------------------------------------------- > > Key: TEIID-4974 > URL: https://issues.jboss.org/browse/TEIID-4974 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 10.0, 8.12.x-6.4, 9.3.1 > > > Teiid's SQL function TRANSLATE is translated to N1QL REPLACE function, but those functions are not equivalent. > See the difference: > https://developer.couchbase.com/documentation/server/current/n1ql/n1ql-la... > https://teiid.gitbooks.io/documents/content/reference/String_Functions.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4969) Couchbase - ORDER BY returns empty result

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4969?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4969. ----------------------------------- Resolution: Done > Couchbase - ORDER BY returns empty result > ----------------------------------------- > > Key: TEIID-4969 > URL: https://issues.jboss.org/browse/TEIID-4969 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 10.0, 8.12.x-6.4, 9.3.1 > > > Issuing query like \[1\] returns empty result. From what I can see, query seems to not be properly translated to the source-specific query \[2\]. > {code:sql|title=\[1\] Query} > SELECT IntKey AS Total FROM BQT1.SmallA ORDER BY IntKey > {code} > {code:plain|title=\[2\] Source-specific query - c_0 is not defined anywhere} > 09:40:11,748 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue60) TEIID29001 Source-specific Query: SELECT `$cb_c1_IntKey` FROM `dvqe_small` `$cb_t1` LET `$cb_c1_IntKey` = `$cb_t1`.`IntKey`c_0 WHERE `$cb_t1`.`type` = 'SmallA' ORDER BY c_0 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4973) Couchbase - Teiid returns empty result if source query fails

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4973?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4973. ----------------------------------- Resolution: Done > Couchbase - Teiid returns empty result if source query fails > ------------------------------------------------------------ > > Key: TEIID-4973 > URL: https://issues.jboss.org/browse/TEIID-4973 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 10.0, 8.12.x-6.4, 9.3.1 > > > Teiid does not provide any information to the user that query actually failed. Only empty result is returned. > Currently, issuing query like \[1\] produces source-specific query with syntax error \[2\] (result directly from Couchbase \[3\]). But Teiid returns empty result just like query succeeded with no rows. > {code:sql|title=\[1\] Query} > SELECT BQT1.SmallA.FloatNum FROM BQT1.SmallA WHERE BQT1.SmallA.FloatNum = 7 > {code} > {code:plain|title=\[2\] Source-specific query} > 10:16:09,749 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue86) TEIID29001 Source-specific Query: SELECT TONUMBER(`$cb_c1_FloatNum`) FROM `dvqe_small` `$cb_t1` LET `$cb_c1_FloatNum` = `$cb_t1`.`FloatNum`TONUMBER() WHERE TONUMBER(`$cb_c1_FloatNum`) = 7.0 AND `$cb_t1`.`type` = 'SmallA' > {code} > {code:plain|title=\[3\] Couchbase result} > [ > { > "code": 3000, > "msg": "syntax error - at TONUMBER", > "query_from_user": "SELECT TONUMBER(`$cb_c1_FloatNum`) FROM `dvqe_small` `$cb_t1` LET `$cb_c1_FloatNum` = `$cb_t1`.`FloatNum`TONUMBER() WHERE TONUMBER(`$cb_c1_FloatNum`) = 7.0 AND `$cb_t1`.`type` = 'SmallA'" > } > ] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4970) Couchbase - GROUP BY returns empty result

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4970?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4970. ----------------------------------- Resolution: Done > Couchbase - GROUP BY returns empty result > ----------------------------------------- > > Key: TEIID-4970 > URL: https://issues.jboss.org/browse/TEIID-4970 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 10.0, 8.12.x-6.4, 9.3.1 > > > Issuing query like \[1\] returns empty result. Query seems to not be properly translated to source-specific query \[2\] > {code:sql|title=\[1\] Query} > SELECT IntKey, SUM(IntKey) AS Total FROM BQT1.SmallA GROUP BY IntKey > {code} > {code:plain|title=\[2\] Source-specific query - GROUP BY clause refers to cb_c2 instead of cb_c1} > 09:53:09,066 DEBUG [org.teiid.CONNECTOR] (Worker5_QueryProcessorQueue64) TEIID29001 Source-specific Query: SELECT `$cb_c1_IntKey`, SUM(`$cb_c2_IntKey`) FROM `dvqe_small` `$cb_t1` LET `$cb_c1_IntKey` = `$cb_t1`.`IntKey`, `$cb_c2_IntKey` = `$cb_t1`.`IntKey` WHERE `$cb_t1`.`type` = 'SmallA' GROUP BY `$cb_c2_IntKey` > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4975) Couchbase - SUBSTRING function is not translated correctly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4975?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4975. ----------------------------------- Resolution: Done > Couchbase - SUBSTRING function is not translated correctly > ---------------------------------------------------------- > > Key: TEIID-4975 > URL: https://issues.jboss.org/browse/TEIID-4975 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 10.0, 8.12.x-6.4, 9.3.1 > > > Teiid's SQL function SUBSTRING(x,y \[, z\]) is translated to N1QL substring(x,y \[, z\]) function, but correct N1QL function is called SUBSTR. > Documentation: https://developer.couchbase.com/documentation/server/current/n1ql/n1ql-la... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4957) Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4957?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4957: ------------------------------------ In Teiid Designer, you can add a User Property to the VDB for connection-type = NONE. > Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-4957 > URL: https://issues.jboss.org/browse/TEIID-4957 > Project: Teiid > Issue Type: Bug > Components: VDB > Affects Versions: 8.12.10.6_3 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Fix For: 10.0 > > > After deploying a VDB to a managed server group, set the Connection type to anything but the default of By_Version, so None or Any. Now restart the server and you'll see the Connection type is reset to the default. > What I see is that when the change is made a vdb.xml with that new connection-type is written to the /DVserverhome/domain/servers/server-two/data/teiid-data/SampleVDB_1 folder, this folder is deleted upon a restart though so the change is not kept. > This only happens in Domain mode, running in Standalone mode saves the change because the teiid-data is not deleted on a restart. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4980) arche-type parent not available in maven

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4980?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4980. ----------------------------------- Resolution: Done The 9.0.0 version will now work as expected. > arche-type parent not available in maven > ---------------------------------------- > > Key: TEIID-4980 > URL: https://issues.jboss.org/browse/TEIID-4980 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 9.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > The translator archetype was updated for 9.0.0, but the parent was not pushed to maven: > Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate (default-cli) on project standalone-pom: The desired archetype does not exist (org.jboss.teiid.arche-types:translator-archetype:9.0.0) > The docs should also be updated to define the available archetype versions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4957) Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-4957?page=com.atlassian.jira.plugin... ] Debbie Steigner commented on TEIID-4957: ---------------------------------------- [~jolee] The workaround is to manually edit the /META-INF/vdb.xml file inside your VDB archive file and set the Connection type before deploying it so that it's permanently set: At the top of the vdb.xml after the description add the connection-type and value. <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <vdb name="sample" version="1"> <description></description> <connection-type>NONE</connection-type> <property name="preview" value="false"/> <property name="validationDateTime" value="Fri Feb 10 07:27:53 CST 2017"/> <property name="validationVersion" value="8.12.8"/> <model name=.... > Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-4957 > URL: https://issues.jboss.org/browse/TEIID-4957 > Project: Teiid > Issue Type: Bug > Components: VDB > Affects Versions: 8.12.10.6_3 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Fix For: 10.0 > > > After deploying a VDB to a managed server group, set the Connection type to anything but the default of By_Version, so None or Any. Now restart the server and you'll see the Connection type is reset to the default. > What I see is that when the change is made a vdb.xml with that new connection-type is written to the /DVserverhome/domain/servers/server-two/data/teiid-data/SampleVDB_1 folder, this folder is deleted upon a restart though so the change is not kept. > This only happens in Domain mode, running in Standalone mode saves the change because the teiid-data is not deleted on a restart. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4957) Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4957?page=com.atlassian.jira.plugin... ] Johnathon Lee commented on TEIID-4957: -------------------------------------- [~rareddy] possibly I'm misunderstanding... is the workaround to be applied on every restart in domain mode? Can you detail the workaround in the "workaround' field on this jira? > Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-4957 > URL: https://issues.jboss.org/browse/TEIID-4957 > Project: Teiid > Issue Type: Bug > Components: VDB > Affects Versions: 8.12.10.6_3 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Fix For: 10.0 > > > After deploying a VDB to a managed server group, set the Connection type to anything but the default of By_Version, so None or Any. Now restart the server and you'll see the Connection type is reset to the default. > What I see is that when the change is made a vdb.xml with that new connection-type is written to the /DVserverhome/domain/servers/server-two/data/teiid-data/SampleVDB_1 folder, this folder is deleted upon a restart though so the change is not kept. > This only happens in Domain mode, running in Standalone mode saves the change because the teiid-data is not deleted on a restart. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4976) criteria duplicated when criteria includes the same columns as dependent join criteria

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4976?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4976: ------------------------------- Fix Version/s: 8.12.12.6_3 > criteria duplicated when criteria includes the same columns as dependent join criteria > -------------------------------------------------------------------------------------- > > Key: TEIID-4976 > URL: https://issues.jboss.org/browse/TEIID-4976 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.11.6_2 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 10.0, 8.12.x-6.4, 8.12.12.6_3, 8.7.13.6_2 > > > Submitting a query that uses the same column for the join condition and criteria results in the criteria being duplicated on the dependent side of the join. > For example: > SELECT * FROM A, B > WHERE B.id = A.id AND A.id IN ('1','2','3') OPTION MAKEDEP B; > Results in the dependent side query looking like: > SELECT ... FROM B WHERE B.id IN ('1','2','3') AND B.id IN ('1','2','3'); > This looks to have already been resolved in later versions, but I was not able to find the original JIRA that would have addressed this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2017