March 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3994) AliasSymbol wrapping AliasSymbol error

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3994?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3994: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1314909|https://bugzilla.redhat.com/show_bug.cgi?id=1314909] from ON_QA to VERIFIED > AliasSymbol wrapping AliasSymbol error > -------------------------------------- > > Key: TEIID-3994 > URL: https://issues.jboss.org/browse/TEIID-3994 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1.6_2 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > Attachments: Oracle.PNG, SQLServer.PNG > > > I've defined a view and overrode the default triggers for Select, Insert, Update, and Delete. I overrode the triggers because the select is returning "hardcoded" values for a few fields (calling them virtual columns). The Update and Insert triggers will ignore these hardcoded values just in case the caller tries to update a virtual column. > I'm trying to run a insert into <tableA> select * from <tableB> query. When I run this, I get an error org.teiid.jdbc.TeiidSQLException: Cannot create AliasSymbol wrapping AliasSymbol. > Facts: > -- I can insert a record if I only select one column from tableB. > -- If I select two or more columns, it throws the error every time. > -- If I remove the overridden triggers, the insert into <tableA> select * from <tableB> works fine. > -- I can insert one or more columns into <tableA> when *not* using a insert into <tableA> select * from <tableB> query > -- Table A is Oracle > -- Table B is SQL Server > My hunch is the generated query (hibernate, or whatever SQL generator) is choking with the overridden trigger. Perhaps this use-case slipped through testing, or even more probable, I made a mistake in the trigger creation. > Here's a snip of the insert trigger, with a lot of fields removed for simplicity. > {code} > FOR EACH ROW > BEGIN ATOMIC > INSERT INTO <schema>.<tableA> (SourceSystemID, RecordTypeID, BatchID ...) > VALUES ( > convert("NEW".SourceSystemID, short), > convert("NEW".RecordTypeID, short), > convert("NEW".BatchID, integer) > ... > ) > END > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4017) EXECUTE IMMEDIATE in anonymous procedure ignores permissions

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4017?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4017: ------------------------------------- [~shawkins]. Did you addressed also case if user invokes testSelect2() \[2\]? See the last paragraph of 'Steps to Reproduce'. Teiid still allows user to execute such procedure. \[2\] {code:sql} SELECT s.* FROM (call procs.testSelect2()) AS s {code} > EXECUTE IMMEDIATE in anonymous procedure ignores permissions > ------------------------------------------------------------ > > Key: TEIID-4017 > URL: https://issues.jboss.org/browse/TEIID-4017 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12 > Environment: teiid-8.12-Beta1 on Red Hat JBoss Enterprise Application Platform - Version 6.3.0.GA > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2 > > > I've found a bug when executing a query in the EXECUTE IMMEDIATE clause. It ignores permissions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4015) Error or incorrect value when there is a conflict between local and correlated names

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4015?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4015: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1314538|https://bugzilla.redhat.com/show_bug.cgi?id=1314538] from ON_QA to VERIFIED > Error or incorrect value when there is a conflict between local and correlated names > ------------------------------------------------------------------------------------ > > Key: TEIID-4015 > URL: https://issues.jboss.org/browse/TEIID-4015 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2 > > > With a query such as: > select e1, (select e1 from (select t1.e1 from pm1.g1 as t1) as t2 where t2.e1 = t1.e1) from pm2.g1 as t1 > The correlated reference to t1.e1 will get evaulated as if it were a local value from pm1.g1 as t1 instead. This is because the evaluator doesn't immediately look for the context value, but rather calls to internalEvaluate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4111) Impala translator - add all date pushdown functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4111?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4111: ---------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/652 Thanks Don for contributing this. I'll have it reviewed in time for the next 9.0 pre-release. > Impala translator - add all date pushdown functions > --------------------------------------------------- > > Key: TEIID-4111 > URL: https://issues.jboss.org/browse/TEIID-4111 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 8.13.3 > Reporter: Don Krapohl > Assignee: Steven Hawkins > > As a teiid client I need the ability to perform date-based operations in the impala data store (data functions pushed down to impala) instead of within teiid. > Please add the impala date functions from http://www.cloudera.com/documentation/archive/impala/2-x/2-0-x/topics/imp... > Version 1.0.1 function support list is at http://www.cloudera.com/documentation/archive/impala/1-x/1-0-1/Installing... > Version 1.2.4 function support list is at http://www.cloudera.com/documentation/archive/impala/1-x/1-2-4/Installing... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4110) Odata - date functions does't accept date string as a parameter

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4110?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4110. --------------------------------- Fix Version/s: 9.0 8.12.5 Resolution: Done I could not seem recreate with updated Olingo 4.2 libraries, so as part of resolution I wrote couple unit tests to assert the behavior > Odata - date functions does't accept date string as a parameter > --------------------------------------------------------------- > > Key: TEIID-4110 > URL: https://issues.jboss.org/browse/TEIID-4110 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Michal Sanitrak > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > Date functions year, month, day, hour, minute and second doesn't accept date string(DateTimeOffset) as a parameter. > Reference service which supports OData V4: > *ULR:* http://services.odata.org/V4/Northwind/Northwind.svc/Employees/?$filter=m... eq EmployeeID > *Result:* Employee with ID 1 > *URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleDataTable/?$filter... eq intkey > *Result:* {"error": {"code": null, "message": "TEIID30069 The function 'MONTH(?)' has more than one possible signature." }} > *Expected result:* Entity with intkey 1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4105) ODATA: Duplicate NavigationProperty name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4105?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4105. --------------------------------- Resolution: Done > ODATA: Duplicate NavigationProperty name > ---------------------------------------- > > Key: TEIID-4105 > URL: https://issues.jboss.org/browse/TEIID-4105 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.3 > Reporter: Ivan Lucas Vargas > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 9.0, 8.12.5 > > > Entity 1: TransferRule > Entity 2: FinancialAccount > TransferRule > - sourceAccount : FinancialAccount > - destination : FinancialAccount > - other attributes > the mapping to this for odata resolves to > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" /> > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule" > ToRole="financialaccount" /> > The navigation property name is duplicated with in transfer rule entity. > Hence some of the Odata client see it as ambiguous element > Is there a way to customise the Name to > Name="src_financialaccount" and > Name="dest_financialaccount" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4108) Embedded examples need to mention the Teiid project version

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4108?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4108. ----------------------------------- Resolution: Done Updated the pom to a non-snapshot and added a doc note about the version in general. > Embedded examples need to mention the Teiid project version > ----------------------------------------------------------- > > Key: TEIID-4108 > URL: https://issues.jboss.org/browse/TEIID-4108 > Project: Teiid > Issue Type: Quality Risk > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > The embedded examples currently default to a snapshot version - this should be a released version instead. Also the example docs should mention retargeting the version. > It may also be needed for each of the examples to reference the parent settings.xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4105) ODATA: Duplicate NavigationProperty name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4105?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4105: ------------------------------------- V4 will not be affected because there we are using the FK name as the navigation name, in V2 we used table name to be "user friendly" for navigation property. I could switch this to FK name but that will break the current implementations, so, I am going to use table, table1, table2 scheme name pattern for the navigation name > ODATA: Duplicate NavigationProperty name > ---------------------------------------- > > Key: TEIID-4105 > URL: https://issues.jboss.org/browse/TEIID-4105 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.3 > Reporter: Ivan Lucas Vargas > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 9.0, 8.12.5 > > > Entity 1: TransferRule > Entity 2: FinancialAccount > TransferRule > - sourceAccount : FinancialAccount > - destination : FinancialAccount > - other attributes > the mapping to this for odata resolves to > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" /> > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule" > ToRole="financialaccount" /> > The navigation property name is duplicated with in transfer rule entity. > Hence some of the Odata client see it as ambiguous element > Is there a way to customise the Name to > Name="src_financialaccount" and > Name="dest_financialaccount" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4106) Rename and align infinispan translators/resource-adapters for their purpose

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4106?page=com.atlassian.jira.plugin... ] Work on TEIID-4106 started by Van Halbert. ------------------------------------------ > Rename and align infinispan translators/resource-adapters for their purpose > ---------------------------------------------------------------------------- > > Key: TEIID-4106 > URL: https://issues.jboss.org/browse/TEIID-4106 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.0 > > > The infinispan-cache and infinispan-cache-dsl translators/resource-adapters need to be renamed and aligned for what their purpose is. Because using "dsl" as part of the name is confusing, because both translators now support querying using JDG DSL language. > infinispan-cache: > - rename to infinispan-cache-library-mode (or leave as infinispan-cache and it be assume library mode) > - deprecate the access to remote-cache because the other infinispan-cache-dsl translator provides this feature. > - this will enable the cleaning of the documentation to be specific to library mode > infinispan-cache-dsl: > - rename to infinispan-cache-hot-rod (or something other than "dsl") because this all about remote cache access using hot rod client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4111) Impala translator - add all date pushdown functions

by Don Krapohl (JIRA)

Don Krapohl created TEIID-4111: ---------------------------------- Summary: Impala translator - add all date pushdown functions Key: TEIID-4111 URL: https://issues.jboss.org/browse/TEIID-4111 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 8.13.3 Reporter: Don Krapohl Assignee: Steven Hawkins As a teiid client I need the ability to perform date-based operations in the impala data store (data functions pushed down to impala) instead of within teiid. Please add the impala date functions from http://www.cloudera.com/documentation/archive/impala/2-x/2-0-x/topics/imp... Version 1.0.1 function support list is at http://www.cloudera.com/documentation/archive/impala/1-x/1-0-1/Installing... Version 1.2.4 function support list is at http://www.cloudera.com/documentation/archive/impala/1-x/1-2-4/Installing... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 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 March 2016