April 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4150) Infinispan dsl resource-adapter has not valid module.xml

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4150?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4150: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/678 > Infinispan dsl resource-adapter has not valid module.xml > -------------------------------------------------------- > > Key: TEIID-4150 > URL: https://issues.jboss.org/browse/TEIID-4150 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Jan Stastny > Assignee: Van Halbert > > There is a problem in mentioned module when server attempts to load it: > {code:plain} > [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=infinispandsl:add(module=org.jboss.teiid.resource-adapter.infinispan.dsl) > { > "outcome" => "failed", > "failure-description" => "JBAS010473: Failed to load module for RA [org.jboss.teiid.resource-adapter.infinispan.dsl]", > "rolled-back" => true > } > {code} > It is not valid module according to the 'urn:jboss:module:1.1' schema. > Problematic fragment: > {code:xml} > <dependencies> > ... > <module name="org.infinispan.query" slot="jdg-6.6" optional="true" export="true" services="true" /> > ... > </dependencies> > {code} > According to the mentioned schema the attribute 'services' can have only values: > * none > * import > * export > This issue prevents a user from using the adapter. > Furthermore I am not sure that name 'org.infinispan.query' of the dependency module is correct. I haven't found such module in jdg client libs, there are two possible candidates though: > * org.infinispan.query.dsl > * org.infinispan.query.remote.client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4064) OData - missing non-nullable property

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4064?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4064: ------------------------------------- I have exact same example here https://github.com/teiid/teiid/blob/63-8.12.x/olingo/src/test/java/org/te... as unit test > OData - missing non-nullable property > ------------------------------------- > > Key: TEIID-4064 > URL: https://issues.jboss.org/browse/TEIID-4064 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.0, 8.12.5 > > > Change DDL for tables Customer and Orders in VDB as follows: > {code:sql} > CREATE FOREIGN TABLE Customers ( > id integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'), > name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.CUSTOMERS'); > CREATE FOREIGN TABLE Orders ( > id integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'), > customerid integer, > place varchar(10), > FOREIGN KEY (customerid) REFERENCES Customers(id)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.ORDERS'); > {code} > Note, that both tables have same name of primary key named "id". > Invoke GET method to URL http://localhost:8080/odata4/olingo_basic/Source/Customers/?$count=true&$... > *Result:* > {code:xml} > <error> > <code>400</code> > <message>The non-nullable property 'id' is missing.</message> > </error> > {code} > Here are selected part of Teiid's log: > *Query:* > {code:sql} > SELECT g10.id, g10.name, g11.id, g11.customerid, g11.place FROM Source.Customers AS g10 LEFT OUTER JOIN Source.Orders AS g11 ON g10.id = g11.customerid ORDER BY g10.id > {code} > *Result:* > |id|name|id|customerid|place| > |1|customer1|1|1|town| > |1|customer1|2|1|state| > |1|customer1|3|1|country| > |1|customer1|4|1|abroad| > |2|customer2|5|2|state| > |2|customer2|6|2|country| > |3|customer3|7|3|town| > |3|customer3|8|3|town| > |4|customer4|<null>|<null>|<null>| -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4054) OData - creation of entity (POST) returns exception (status code 500)

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4054?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4054: ------------------------------------- Will also do as part of https://issues.apache.org/jira/browse/OLINGO-939 > OData - creation of entity (POST) returns exception (status code 500) > --------------------------------------------------------------------- > > Key: TEIID-4054 > URL: https://issues.jboss.org/browse/TEIID-4054 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Labels: alpha3 > Fix For: 9.0, 8.12.5 > > > Creation of entity returns exception \[1\]. Representation of entity \[2\]. Http request \[3\]. Header \[4\]. Same exception with of JSON format. > \[1\] > {code:plain} > TEIID10076 Invalid conversion from type class java.lang.Object with value 'java.util.GregorianCalendar[time=4000,areFieldsSet=true,areAllFieldsSet=true, > lenient=true,zone=sun.util.calendar.ZoneInfo[id="GMT",offset=0,dstSavings=0,useDaylight=false,transitions=0,lastRule=null],f > irstDayOfWeek=2,minimalDaysInFirstWeek=4,ERA=1,YEAR=1970,MONTH=0,WEEK_OF_YEAR=1, > WEEK_OF_MONTH=1,DAY_OF_MONTH=1,DAY_OF_YEAR=1,DAY_OF_WEEK=5,DAY_OF_WEEK_IN_MONTH=1, > AM_PM=0,HOUR=0,HOUR_OF_DAY=0,MINUTE=0,SECOND=4,MILLISECOND=0,ZONE_OFFSET=0,DST_OFFSET=0]' > to type class java.sql.Time > {code} > \[2\] > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <entry xmlns="http://www.w3.org/2005/Atom" xmlns:d="http://docs.oasis-open.org/odata/ns/data" xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml" xmlns:m="http://docs.oasis-open.org/odata/ns/metadata"> > <category scheme="http://docs.oasis-open.org/odata/ns/scheme" /> > <content type="application/xml"> > <m:properties> > <d:intkey m:type="Int32">4</d:intkey> > <d:intnum m:type="Int32">4</d:intnum> > <d:stringkey>4</d:stringkey> > <d:stringval>value_4</d:stringval> > <d:booleanval m:type="Boolean">false</d:booleanval> > <d:decimalval m:type="Double">-20.4</d:decimalval> > <d:timeval m:type="TimeOfDay">00:00:04</d:timeval> > <d:dateval m:type="Date">2004-04-04</d:dateval> > <d:timestampval m:type="DateTimeOffset">2004-01-01T00:00:04Z</d:timestampval> > <d:clobval m:type="Binary">Y2xvYl92YWx1ZV8wMDAwNA==</d:clobval> > </m:properties> > </content> > </entry> > {code} > \[3\] > POST http://localhost:8080/odata4/olingo_basic/Source/PostTable(4) > \[4\] > Content-type: application/xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4164) Correct the transitive dependencies in OData4 translator

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-4164: ----------------------------------- Summary: Correct the transitive dependencies in OData4 translator Key: TEIID-4164 URL: https://issues.jboss.org/browse/TEIID-4164 Project: Teiid Issue Type: Quality Risk Components: OData Affects Versions: 9.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Minor Currently "com.fasterxml" transitive dependencies are not in "kits" or pom.xml They need to be explicitly defined as dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4143) Wrong Content-Type in error response from odata

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4143?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4143: ------------------------------------- Added upstream JIRA https://issues.apache.org/jira/browse/OLINGO-939 > Wrong Content-Type in error response from odata > ----------------------------------------------- > > Key: TEIID-4143 > URL: https://issues.jboss.org/browse/TEIID-4143 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 8.12.5 > > > When submitting an odata request that causes an error on server side, the response has the Content-Type header set to just "application", which causes clients to fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4160) Impala - result set is not sorted if ORDER BY is defined in query

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4160?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4160: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1329178|https://bugzilla.redhat.com/show_bug.cgi?id=1329178] from NEW to MODIFIED > Impala - result set is not sorted if ORDER BY is defined in query > ----------------------------------------------------------------- > > Key: TEIID-4160 > URL: https://issues.jboss.org/browse/TEIID-4160 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.x > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.0, 8.12.5, 8.13.4 > > > Query: > {code:sql} > SELECT g_1.StringNum AS c_0 FROM Source.SmallA AS g_1 WHERE g_1.IntKey <= 50 UNION ALL SELECT g_0.StringNum AS c_0 FROM Source.SmallB AS g_0 WHERE g_0.IntKey > 50 ORDER BY c_0 > {code} > Result: as you can see, nulls are not next to each other > |StringNum| > |-24| > |<null>| > |-14| > |-13| > |-12| > |-11| > |-10| > |-9| > |-8| > |<null>| > |-6 > |-5| > |...| > Expected result: this is result of simple query SELECT stringnum FROM source.smalla ORDER BY 1 > |StringNum| > |-1| > |-10| > |-11| > |-12| > |-13| > |-14| > |-15| > |...| -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4160) Impala - result set is not sorted if ORDER BY is defined in query

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4160?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4160: ---------------------------------- Component/s: JDBC Connector Fix Version/s: 9.0 8.12.5 8.13.4 Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1329178 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1329178, https://bugzilla.redhat.com/show_bug.cgi?id=1329339) Priority: Blocker (was: Major) > Impala - result set is not sorted if ORDER BY is defined in query > ----------------------------------------------------------------- > > Key: TEIID-4160 > URL: https://issues.jboss.org/browse/TEIID-4160 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.x > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.0, 8.12.5, 8.13.4 > > > Query: > {code:sql} > SELECT g_1.StringNum AS c_0 FROM Source.SmallA AS g_1 WHERE g_1.IntKey <= 50 UNION ALL SELECT g_0.StringNum AS c_0 FROM Source.SmallB AS g_0 WHERE g_0.IntKey > 50 ORDER BY c_0 > {code} > Result: as you can see, nulls are not next to each other > |StringNum| > |-24| > |<null>| > |-14| > |-13| > |-12| > |-11| > |-10| > |-9| > |-8| > |<null>| > |-6 > |-5| > |...| > Expected result: this is result of simple query SELECT stringnum FROM source.smalla ORDER BY 1 > |StringNum| > |-1| > |-10| > |-11| > |-12| > |-13| > |-14| > |-15| > |...| -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4160) Impala - result set is not sorted if ORDER BY is defined in query

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4160?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4160. ----------------------------------- Resolution: Done Elevated the order by and limit above the inline view. > Impala - result set is not sorted if ORDER BY is defined in query > ----------------------------------------------------------------- > > Key: TEIID-4160 > URL: https://issues.jboss.org/browse/TEIID-4160 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.x > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.0, 8.12.5, 8.13.4 > > > Query: > {code:sql} > SELECT g_1.StringNum AS c_0 FROM Source.SmallA AS g_1 WHERE g_1.IntKey <= 50 UNION ALL SELECT g_0.StringNum AS c_0 FROM Source.SmallB AS g_0 WHERE g_0.IntKey > 50 ORDER BY c_0 > {code} > Result: as you can see, nulls are not next to each other > |StringNum| > |-24| > |<null>| > |-14| > |-13| > |-12| > |-11| > |-10| > |-9| > |-8| > |<null>| > |-6 > |-5| > |...| > Expected result: this is result of simple query SELECT stringnum FROM source.smalla ORDER BY 1 > |StringNum| > |-1| > |-10| > |-11| > |-12| > |-13| > |-14| > |-15| > |...| -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4146) Using JDG Library Mode, unable to perform insert (

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4146?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4146: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1327752|https://bugzilla.redhat.com/show_bug.cgi?id=1327752] from NEW to MODIFIED > Using JDG Library Mode, unable to perform insert ( > -------------------------------------------------- > > Key: TEIID-4146 > URL: https://issues.jboss.org/browse/TEIID-4146 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.5 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > Fix For: 9.0, 8.12.5 > > > Trying to run the JDG local cache quickstart, get the following error when trying to perform an insert: > 15:09:34,027 WARN [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue12) TEIID30020 Processing exception for request O25SlCY41bD5.6 'TEIID30492 Element StockCache.Stock.StockObject of StockCache.Stock is neither nullable nor has a default value. A value must be specified in the insert.'. Originally QueryValidatorException Request.java:330. Enable more detailed logging to see the entire stacktrace. > The issue is because the StockObject column is set to be NullType.unknown, instead of NullType.Nullable. This is because the metadata processor in the translator-object is setting it incorrectly. > Workaround: > - Using Teiid Designer to import the source model and change the null type. > - use dynamic vdb and define the DDL metadata to set the null type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4160) Impala - result set is not sorted if ORDER BY is defined in query

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4160?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4160: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1329339|https://bugzilla.redhat.com/show_bug.cgi?id=1329339] from NEW to ASSIGNED > Impala - result set is not sorted if ORDER BY is defined in query > ----------------------------------------------------------------- > > Key: TEIID-4160 > URL: https://issues.jboss.org/browse/TEIID-4160 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.x > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Query: > {code:sql} > SELECT g_1.StringNum AS c_0 FROM Source.SmallA AS g_1 WHERE g_1.IntKey <= 50 UNION ALL SELECT g_0.StringNum AS c_0 FROM Source.SmallB AS g_0 WHERE g_0.IntKey > 50 ORDER BY c_0 > {code} > Result: as you can see, nulls are not next to each other > |StringNum| > |-24| > |<null>| > |-14| > |-13| > |-12| > |-11| > |-10| > |-9| > |-8| > |<null>| > |-6 > |-5| > |...| > Expected result: this is result of simple query SELECT stringnum FROM source.smalla ORDER BY 1 > |StringNum| > |-1| > |-10| > |-11| > |-12| > |-13| > |-14| > |-15| > |...| -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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