March 2016 - teiid-issues - Jboss List Archives

[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 updated TEIID-4105: -------------------------------- Fix Version/s: 9.0 8.12.5 (was: 8.8) (was: 8.7.1) > 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)

9 years, 9 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-4105: ----------------------------------- Summary: 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: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.8, 8.7.1 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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4094) Move the packaging of teiid-jdbc.jar into is own project

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4094?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4094: --------------------------------------- I can fix this by excluding the modules dependency. The only nuance here is that if you use maven to get the jdbc jar it will be named teiid-jdbc-version.jar, rather than kitted form that will be teiid-version-jdbc.jar. > Move the packaging of teiid-jdbc.jar into is own project > -------------------------------------------------------- > > Key: TEIID-4094 > URL: https://issues.jboss.org/browse/TEIID-4094 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > > The issue with the way the teiid-jdbc.jar is packaged now, is that the teiid-web-console.zip gets included as a dependency. > {code} > [INFO] +- org.jboss.teiid:teiid:jar:jdbc:8.12.5.redhat-2:compile > [INFO] | \- org.jboss.teiid.web-console:teiid-console-dist:zip:jboss-as7:2.5.6.Final-redhat-63-4:compile > {code} > And that becomes an issue when other external projects to Teiid include the jdbc driver as a dependency, in that they also end up requiring the web-console.zip. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3015?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3015: ------------------------------------- If we need to pull into other DV branches then it may be better to open another one. > ODATA: Duplicate NavigationProperty name > ---------------------------------------- > > Key: TEIID-3015 > URL: https://issues.jboss.org/browse/TEIID-3015 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.8, 8.7.1 > > > 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)

9 years, 9 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3015?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3015: --------------------------------------- Yes Ivan there is still an issue. The NativationProperty Relationship name was updated by this issue, but not the Name. Ramesh do you want to reopen this issue or start a new one? > ODATA: Duplicate NavigationProperty name > ---------------------------------------- > > Key: TEIID-3015 > URL: https://issues.jboss.org/browse/TEIID-3015 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.8, 8.7.1 > > > 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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4008) Sending teiid varbinary value (x'') to Microsoft SQL Server errors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4008?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4008: ------------------------------------------------ Alex Szczuczko <aszczucz(a)redhat.com> changed the Status of [bug 1313407|https://bugzilla.redhat.com/show_bug.cgi?id=1313407] from MODIFIED to ON_QA > Sending teiid varbinary value (x'') to Microsoft SQL Server errors > ------------------------------------------------------------------ > > Key: TEIID-4008 > URL: https://issues.jboss.org/browse/TEIID-4008 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.7.2.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2 > > > When sending a query to Microsoft SQL Server with a varbinary in criteria: > select * from debBinary where ipv6= x'FFFF6BBE85D8' > It pushes the criteria to Microsoft SQL Server, but as X'FFFF6BBE85D8'[1] so Microsoft gives the syntax error[2] and needs to just be select * from debBinary where ipv6= 'FFFF6BBE85D8': > [1]14:26:08,951 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8) Source-specific command: SELECT g_0."id", g_0."ipv6" FROM "bqt2"."dbo"."debbinary" g_0 WHERE g_0."ipv6" = X'FFFF6BBE85D8' > [2] com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'FFFF6BBE85D8'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3177) Enforce SSL connections over ODBC when Encryption Mode is enabled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3177?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3177: ------------------------------------------------ Alex Szczuczko <aszczucz(a)redhat.com> changed the Status of [bug 1312455|https://bugzilla.redhat.com/show_bug.cgi?id=1312455] from MODIFIED to ON_QA > Enforce SSL connections over ODBC when Encryption Mode is enabled > ----------------------------------------------------------------- > > Key: TEIID-3177 > URL: https://issues.jboss.org/browse/TEIID-3177 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Affects Versions: 8.8 > Reporter: Cristiano Nicolai > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.9, 8.7.5.6_2 > > > When connecting via ODBC transport, even if the encryption mode is set to enabled is still possible to establish non ssl connections. This allows clients to connect via insecure method. We would like that the Teiid transport could reject connections if they are not properly set up using SSL transport. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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: ------------------------------------------------ Alex Szczuczko <aszczucz(a)redhat.com> changed the Status of [bug 1314538|https://bugzilla.redhat.com/show_bug.cgi?id=1314538] from MODIFIED to ON_QA > 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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3948) Provide a different mechanism to update odata wars

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3948?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3948: ------------------------------------------------ Alex Szczuczko <aszczucz(a)redhat.com> changed the Status of [bug 1305039|https://bugzilla.redhat.com/show_bug.cgi?id=1305039] from MODIFIED to ON_QA > Provide a different mechanism to update odata wars > -------------------------------------------------- > > Key: TEIID-3948 > URL: https://issues.jboss.org/browse/TEIID-3948 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > Directly modifying the wars under the base modules is a bad practice. We need to have users modify non-kit artifact files in a different location. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3978) Remove AddressWrapper

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3978?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3978: ------------------------------------------------ Alex Szczuczko <aszczucz(a)redhat.com> changed the Status of [bug 1308959|https://bugzilla.redhat.com/show_bug.cgi?id=1308959] from MODIFIED to ON_QA > Remove AddressWrapper > --------------------- > > Key: TEIID-3978 > URL: https://issues.jboss.org/browse/TEIID-3978 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2 > > > AddressWrapper was introduced to handle an earlier jgroups version where address objects were not directly serializable. However the deserialization code is using the thread context class loader which is not guaranteed to have the JGroups classes in the classpath. The resulting exception (where the original exception is simply swallowed) looks like: > {code} > 2016-02-16 08:45:30,140 ERROR [Incoming-1,shared=tcp-teiid-1] org.teiid.replication.jgroups.JGroupsObjectReplicator$ReplicatorRpcDispatcher - exception marshalling object > java.lang.IllegalStateException: unread block data > at java.io.ObjectInputStream$BlockDataInputStream.setBlockDataMode(ObjectInputStream.java:2421) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1382) > at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1706) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1344) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at org.jgroups.blocks.MethodCall.readExternal(MethodCall.java:430) > at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1837) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at org.teiid.replication.jgroups.JGroupsObjectReplicator$ContextAwareMarshaller.objectFromBuffer(JGroupsObjectReplicator.java:611) > at org.teiid.replication.jgroups.JGroupsObjectReplicator$ReplicatorRpcDispatcher.handle(JGroupsObjectReplicator.java:106) > at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:484) > at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:391) > at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:249) > at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:600) > at org.jgroups.JChannel.up(JChannel.java:707) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 March 2016