April 2015 - teiid-issues - Jboss List Archives

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

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3112?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3112: --------------------------------- Fix Version/s: 8.7.2 > 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, 6.2-8.7.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.3.11#6341)

9 years, 9 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3112?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3112: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1196318|https://bugzilla.redhat.com/show_bug.cgi?id=1196318] from NEW to MODIFIED > 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, 6.2-8.7.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.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3386) Mixed resutl with (double) full outer join and where clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3386?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3386: ---------------------------------- Workaround Description: Use a preserve hint around from clauses containing multiple full outer joins that can be pushed to oracle: SELECT BQT1.SmallA.IntKey AS SmallA_IntKey, BQT1.MediumB.IntKey AS MediumB_IntKey, BQT1.MediumA.IntKey AS MediumA_IntKey FROM /*+ preserve */ ((BQT1.SmallA FULL OUTER JOIN BQT1.MediumB ON BQT1.SmallA.IntKey = BQT1.MediumB.IntKey) FULL OUTER JOIN BQT1.MediumA ON BQT1.MediumB.IntKey = BQT1.MediumA.IntKey) WHERE BQT1.MediumA.IntKey < 1500 ORDER BY MediumA_IntKey, MediumB_IntKey, SmallA_IntKey Workaround: Workaround Exists Added a workaround. I will likely resolve this without a code change based upon a workaround being available and that this an oracle bug that is addressed on later versions. > Mixed resutl with (double) full outer join and where clause > ----------------------------------------------------------- > > Key: TEIID-3386 > URL: https://issues.jboss.org/browse/TEIID-3386 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Attachments: server.log > > > If a query contains double FULL OUTER JOIN and WHERE clause that contains condition on column from last table, teiid returns mixed result (underlying oracle10). > Query: > SELECT BQT1.SmallA.IntKey AS SmallA_IntKey, BQT2.MediumB.IntKey AS MediumB_IntKey, BQT2.LargeB.IntKey AS LargeB_IntKey > FROM (BQT1.SmallA FULL OUTER JOIN BQT2.MediumB ON BQT1.SmallA.IntKey = BQT2.MediumB.IntKey) FULL OUTER JOIN BQT2.LargeB ON BQT2.MediumB.IntKey = BQT2.LargeB.IntKey > WHERE BQT2.LargeB.IntKey < 1500 ORDER BY LargeB_IntKey, MediumB_IntKey, SmallA_IntKey; > Actual result: > 0 0 0 > 1 1 1 > 2 2 2 > 3 3 3 > ... ... ... > 49 49 49 > 50 50 50 > ... ... ... > 999 999 999 > <null> <null> 1000 > ... ... ... > <null> <null> 1499 > Expected result: > 0 0 0 > 1 1 1 > 2 2 2 > 3 3 3 > ... ... ... > 49 49 49 > <null> 50 50 > ... ... ... > 999 999 999 > <null> <null> 1000 > ... ... ... > <null> <null> 1499 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3409) PostgreSQLExecutionFactory TranslatorProperty annotation in wrong place

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3409?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3409. ----------------------------------- Fix Version/s: 8.10.1 8.11 Resolution: Done > PostgreSQLExecutionFactory TranslatorProperty annotation in wrong place > ----------------------------------------------------------------------- > > Key: TEIID-3409 > URL: https://issues.jboss.org/browse/TEIID-3409 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.11 > Reporter: Kylin Soong > Assignee: Steven Hawkins > Fix For: 8.10.1, 8.11 > > > As [1] it seems PostgreSQLExecutionFactory TranslatorProperty annotation in wrong place. > [1] https://github.com/teiid/teiid/pull/435 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3410) OData object URI does not resolve to a usable URL.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3410?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3410: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1208515 > OData object URI does not resolve to a usable URL. > -------------------------------------------------- > > Key: TEIID-3410 > URL: https://issues.jboss.org/browse/TEIID-3410 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > OData object URI does not resolve to a usable URL. When accessing a VDB via odata with a browser either via JSON or XML the uri listed in the metadata is not valid, it doesn't have the FQN of the table, only the type shows FQN: > "__metadata" : { > "uri" : "http://localhost:8080/odata/ODataRHQ/rhq_agent(10001)", > "type" : "RHQ32.rhq_agent" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3358) Issues with entity set names

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3358: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1208515 > Issues with entity set names > ---------------------------- > > Key: TEIID-3358 > URL: https://issues.jboss.org/browse/TEIID-3358 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.11 > > > The entity set name used for sql generation should be the fully qualified name. If there is for example two table with the same names in schemas visible to odata, but one of the tables does not have a key, then an ambiguous name exception will be thrown if an odata url is used with only the base table name. > It also appears that the URI link in the results metadata uses the non-qualified table name, which will have issues in the scenario above. > We may also need to document or add an additional check for ambiguity as the OData4j findEdmEntitySet logic will return the first matching entity, which is generally against our approach to resolving. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3410) OData object URI does not resolve to a usable URL.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3410?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3410. ----------------------------------- Resolution: Duplicate Issue Addressed by https://issues.jboss.org/browse/TEIID-3358 The full fix was done through an OData4j fork, so if this is needed for backport a different approach may be needed. > OData object URI does not resolve to a usable URL. > -------------------------------------------------- > > Key: TEIID-3410 > URL: https://issues.jboss.org/browse/TEIID-3410 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > OData object URI does not resolve to a usable URL. When accessing a VDB via odata with a browser either via JSON or XML the uri listed in the metadata is not valid, it doesn't have the FQN of the table, only the type shows FQN: > "__metadata" : { > "uri" : "http://localhost:8080/odata/ODataRHQ/rhq_agent(10001)", > "type" : "RHQ32.rhq_agent" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3410) OData object URI does not resolve to a usable URL.

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-3410: -------------------------------------- Summary: OData object URI does not resolve to a usable URL. Key: TEIID-3410 URL: https://issues.jboss.org/browse/TEIID-3410 Project: Teiid Issue Type: Bug Components: OData Affects Versions: 8.7 Reporter: Debbie Steigner Assignee: Steven Hawkins OData object URI does not resolve to a usable URL. When accessing a VDB via odata with a browser either via JSON or XML the uri listed in the metadata is not valid, it doesn't have the FQN of the table, only the type shows FQN: "__metadata" : { "uri" : "http://localhost:8080/odata/ODataRHQ/rhq_agent(10001)", "type" : "RHQ32.rhq_agent" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3395) USER and ROLE tables should be exposed as System Tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3395?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3395. ----------------------------------- Resolution: Won't Fix Marking the original issue as won't fix. We can revisit this if needed for Teiid data role information. > USER and ROLE tables should be exposed as System Tables > ------------------------------------------------------- > > Key: TEIID-3395 > URL: https://issues.jboss.org/browse/TEIID-3395 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Tom Johnston > Assignee: Steven Hawkins > > LIke most databases (i.e. Oracle has DBA_USERS and DBA_ROLES) TeiiD should have the same and be sourced from whatever security domain is being used. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3058) Cassandra: cannot compare timestamp field in where clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3058?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3058: --------------------------------------- The existing logic seems to work fine for Cassandra 2.0.9 with CQL 3.1.1. Can you provide more details about the exception you are now seeing, what version are you using, etc.? > Cassandra: cannot compare timestamp field in where clause > ---------------------------------------------------------- > > Key: TEIID-3058 > URL: https://issues.jboss.org/browse/TEIID-3058 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7, 8.10 > Environment: Cassandra with Teiid 8.7 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > It seems like Teiid is having problem to compare translate CQL if there is timestamp comparison in where clause: > ORIGINAL SQL: > select "cassandrads_sales"."product_family" as "cassandrads_sales_product_family", > "cassandrads_sales"."product_family" as "cassandrads_sales_product_family1" > from "cassandrads"."sales" "cassandrads_sales" > where "cassandrads_sales"."the_date" <= '2013-05-01 00:00:00' > limit 1000 > TRANSLATED CQL: > SELECT cassandrads.sales.product_family FROM cassandrads.sales WHERE cassandrads.sales.the_date <= {ts'2013-05-01 00:00:00.0'} LIMIT 1000 > And I got this error: > Caused by: org.teiid.translator.TranslatorException: line 1:55 no viable alternative at input '2013-05-01 00:00:0 > at org.teiid.translator.cassandra.CassandraQueryExecution.execute(CassandraQueryExecution.java:80) > at org.teiid.translator.cassandra.CassandraQueryExecution.execute(CassandraQueryExecution.java:72) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:325) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) > at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:135) > If it is not possible to do time/ data comparison for CQL, maybe you guys should consider to do it in memory instead. Thanks. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2015