September 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3592) XMLFOREST returns source rather than view column names

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3592?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3592: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1247651|https://bugzilla.redhat.com/show_bug.cgi?id=1247651] from NEW to MODIFIED > XMLFOREST returns source rather than view column names > ------------------------------------------------------ > > Key: TEIID-3592 > URL: https://issues.jboss.org/browse/TEIID-3592 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.2 > > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3586) Literal date comparisons with databasetimezone set are incorrect

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3586?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3586: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1247649|https://bugzilla.redhat.com/show_bug.cgi?id=1247649] from NEW to MODIFIED > Literal date comparisons with databasetimezone set are incorrect > ---------------------------------------------------------------- > > Key: TEIID-3586 > URL: https://issues.jboss.org/browse/TEIID-3586 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12, 8.11.2 > > > If the database timezone property is set and a literal comparison is used, then the date value will be shifted from the local timezone into the database timezone, but it should be the other way around. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3559) Refactor Object and Infinispan translator / connectors

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3559?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3559: --------------------------------------- With JDK 1.8 and maven 3.0.5 I see test failures in TestInfinispanJndiDSLSearch. Running maven with -X I see the classpath: translator-object-8.12.0.Beta4-SNAPSHOT.jar translator-object-8.12.0.Beta4-SNAPSHOT-tests.jar teiid-api-8.12.0.Beta4-SNAPSHOT.jar teiid-common-core-8.12.0.Beta4-SNAPSHOT.jar infinispan-core-6.3.0.Final-redhat-5.jar jgroups-3.2.13.Final-redhat-1.jar jboss-transaction-api_1.1_spec-1.0.1.Final-redhat-2.jar jboss-marshalling-river-1.4.10.Final-redhat-1.jar jboss-marshalling-1.4.10.Final-redhat-1.jar infinispan-commons-6.3.0.Final-redhat-5.jar org.osgi.core-4.2.0.redhat-8.jar org.osgi.compendium-4.3.1.jar infinispan-query-6.3.0.Final-redhat-5.jar infinispan-objectfilter-6.3.0.Final-redhat-5.jar hibernate-hql-parser-1.0.0.CR2-redhat-1.jar antlr-runtime-3.4.jar stringtemplate-3.2.1.jar antlr-2.7.7.redhat-4.jar hibernate-hql-lucene-1.0.0.CR2-redhat-1.jar hibernate-jpa-2.0-api-1.0.1.Final-redhat-2.jar hibernate-search-infinispan-4.6.1.Final-redhat-1.jar jackson-mapper-asl-1.9.9.redhat-4.jar jackson-core-asl-1.9.9.redhat-4.jar infinispan-query-dsl-6.3.0.Final-redhat-5.jar infinispan-lucene-directory-6.3.0.Final-redhat-5.jar connector-api-1.5.jar lucene-core-3.6.2.redhat-8.jar hibernate-search-engine-4.6.1.Final-redhat-1.jar hibernate-commons-annotations-4.0.1.Final-redhat-2.jar avro-1.7.5.redhat-2.jar slf4j-api-1.7.2.redhat-3.jar lucene-facet-3.6.2.redhat-6.jar hibernate-search-analyzers-4.6.1.Final-redhat-1.jar lucene-analyzers-3.6.2.redhat-6.jar solr-analysis-extras-3.6.2.redhat-6.jar solr-core-3.6.2.redhat-6.jar solr-solrj-4.6.0.jar noggit-0.5.jar httpclient-4.3.6.jar httpcore-4.3.3.jar httpmime-4.3.6.jar commons-codec-1.9.jar commons-io-2.1.0.redhat-4.jar commons-lang-2.6.0.redhat-4.jar jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar mockito-all-1.9.5.jar teiid-api-8.12.0.Beta4-SNAPSHOT-tests.jar teiid-engine-8.12.0.Beta4-SNAPSHOT-tests.jar Saxon-HE-9.5.1-6.jar nux-1.6.jar jts-1.13.jar jts2geojson-0.4.0.jar jackson-databind-2.4.2.jar jackson-core-2.4.2.jar jackson-annotations-2.4.2.jar proj4j-0.1.0.jar xom-1.2.7.redhat-4.jar jaxen-1.1.4.jar teiid-common-core-8.12.0.Beta4-SNAPSHOT-tests.jar teiid-client-8.12.0.Beta4-SNAPSHOT.jar teiid-admin-8.12.0.Beta4-SNAPSHOT.jar teiid-engine-8.12.0.Beta4-SNAPSHOT.jar teiid-metadata-8.12.0.Beta4-SNAPSHOT.jar teiid-metadata-8.12.0.Beta4-SNAPSHOT-tests.jar jboss-vfs-3.2.2.Final-redhat-1.jar jboss-logging-3.1.4.GA-redhat-1.jar junit-4.11.jar hamcrest-core-1.3.jar surefire-junit4-2.17.jar which versions or orderings seem incorrect? > Refactor Object and Infinispan translator / connectors > ------------------------------------------------------ > > Key: TEIID-3559 > URL: https://issues.jboss.org/browse/TEIID-3559 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > > Now that JDG has reworked its remote-cache and changed (reduced) what dependencies its exposed, there's now more common code between the object/infinispan-cache translator/connector and the infinispan-cache-dsl translator/connector. I think refactoring can eliminate issues with support and ensure common behavior across all the code. > Where is common code seen: > - searching (i.e., DSLSearch) > - updates (InfinispanUpdateExecution) > - ClassRegistry > (for starters) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3534) Infinispan-dsl-cache translator: can't insert null into column of type boolean

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3534?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3534: ------------------------------------------------ David Le Sage <dlesage(a)redhat.com> changed the Status of [bug 1232236|https://bugzilla.redhat.com/show_bug.cgi?id=1232236] from MODIFIED to CLOSED > Infinispan-dsl-cache translator: can't insert null into column of type boolean > ------------------------------------------------------------------------------ > > Key: TEIID-3534 > URL: https://issues.jboss.org/browse/TEIID-3534 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Filip Elias > Assignee: Van Halbert > Attachments: server.log, testVDB.vdb > > > Inserting null into boolean column causes exception. > Sample queries: > {code} > insert into smalla(intKey, stringKey,booleanValue) values(128,'ss',null); > insert into smalla(intKey, stringKey) values(128,'ss'); > {code} > This query works: > {code} > insert into smalla(intKey, stringKey,booleanValue) values(128,'ss',false); > {code} > Exception: > {code} > Connector worker process failed for atomic-request=NuZ8Nt3h1bKx.52.0.44: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[239] returned server error (status=0x85): org.hibernate.search.bridge.BridgeException: Exception while calling bridge#set > class: org.infinispan.query.remote.indexing.ProtobufValueWrapper > path: > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:298) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:88) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:74) > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56) > {code} > This bug breaks data integrity. If this exception is thrown, data will be inserted but it won't be indexed. > The whole exception is in the attachment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3386?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3386: ------------------------------------------------ David Le Sage <dlesage(a)redhat.com> changed the Status of [bug 1202847|https://bugzilla.redhat.com/show_bug.cgi?id=1202847] from MODIFIED to CLOSED > 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.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3728) WS Translator: The format for multiple header values is incorrect

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3728?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3728: ------------------------------------- Looks like Array value is also correct, all the examples point to that. I am working with IIS server at [1] that does not seem to like it. I will add as configuration, so that we do not mess up others. [1] http://services.odata.org/V4/(S(f03od0zmbulfyazmw1eqnd4q))/TripPinServiceRW/ > WS Translator: The format for multiple header values is incorrect > ----------------------------------------------------------------- > > Key: TEIID-3728 > URL: https://issues.jboss.org/browse/TEIID-3728 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.12 > > > Per [1], the request headers with multiple values passed in must be concatenated with comma (,) rather than represented as array > [1] http://stackoverflow.com/questions/3096888/standard-for-adding-multiple-v... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3728) WS Translator: The format for multiple header values is incorrect

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3728?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3728: --------------------------------------- Are you talking about the json value? It is correct to have that as an array - MessageContext.HTTP_REQUEST_HEADERS expects a map<string, list<string>> > WS Translator: The format for multiple header values is incorrect > ----------------------------------------------------------------- > > Key: TEIID-3728 > URL: https://issues.jboss.org/browse/TEIID-3728 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.12 > > > Per [1], the request headers with multiple values passed in must be concatenated with comma (,) rather than represented as array > [1] http://stackoverflow.com/questions/3096888/standard-for-adding-multiple-v... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3728) WS Translator: The format for multiple header values is incorrect

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3728: ----------------------------------- Summary: WS Translator: The format for multiple header values is incorrect Key: TEIID-3728 URL: https://issues.jboss.org/browse/TEIID-3728 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.12 Per [1], the request headers with multiple values passed in must be concatenated with comma (,) rather than represented as array [1] http://stackoverflow.com/questions/3096888/standard-for-adding-multiple-v... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3559) Refactor Object and Infinispan translator / connectors

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3559?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3559: ------------------------------------ Sorry about that. PR: https://github.com/teiid/teiid/pull/532 > Refactor Object and Infinispan translator / connectors > ------------------------------------------------------ > > Key: TEIID-3559 > URL: https://issues.jboss.org/browse/TEIID-3559 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > > Now that JDG has reworked its remote-cache and changed (reduced) what dependencies its exposed, there's now more common code between the object/infinispan-cache translator/connector and the infinispan-cache-dsl translator/connector. I think refactoring can eliminate issues with support and ensure common behavior across all the code. > Where is common code seen: > - searching (i.e., DSLSearch) > - updates (InfinispanUpdateExecution) > - ClassRegistry > (for starters) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3559) Refactor Object and Infinispan translator / connectors

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3559?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3559: --------------------------------------- > Hm, as to the test failure, will have to look at it, because my build passed just before commit. Should I go ahead and make a stab at correcting this? > Refactor Object and Infinispan translator / connectors > ------------------------------------------------------ > > Key: TEIID-3559 > URL: https://issues.jboss.org/browse/TEIID-3559 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > > Now that JDG has reworked its remote-cache and changed (reduced) what dependencies its exposed, there's now more common code between the object/infinispan-cache translator/connector and the infinispan-cache-dsl translator/connector. I think refactoring can eliminate issues with support and ensure common behavior across all the code. > Where is common code seen: > - searching (i.e., DSLSearch) > - updates (InfinispanUpdateExecution) > - ClassRegistry > (for starters) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 September 2015