[JBoss JIRA] (TEIID-3438) Null value returned from BlobImpl getBytes
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3438?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3438:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1212852|https://bugzilla.redhat.com/show_bug.cgi?id=1212852] from ON_QA to VERIFIED
> Null value returned from BlobImpl getBytes
> ------------------------------------------
>
> Key: TEIID-3438
> URL: https://issues.jboss.org/browse/TEIID-3438
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Fix For: 8.7.1.6_2, 8.10.1, 8.11
>
> Attachments: TEIID-3438.zip
>
>
> If translator retrieveValue return a empty Blob, the engine will throw NPE as below
> Caused by: java.lang.NullPointerException
> at javax.sql.rowset.serial.SerialBlob.<init>(SerialBlob.java:100)
> at org.teiid.common.buffer.LobManager.persistLob(LobManager.java:226)
> at org.teiid.common.buffer.LobManager.updateReferences(LobManager.java:141)
> at org.teiid.common.buffer.TupleBuffer.addTupleBatch(TupleBuffer.java:203)
> at org.teiid.query.processor.BatchCollector.flushBatchDirect(BatchCollector.java:229)
> at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:653)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3568) Order By and Limit are not getting pushed to the database, when Union and join are used together.
by Guru Prasad (JIRA)
[ https://issues.jboss.org/browse/TEIID-3568?page=com.atlassian.jira.plugin... ]
Guru Prasad commented on TEIID-3568:
------------------------------------
I have tried analyzing the plan for a similar query(PushOrderByLimitTest1.java) using
teiid-engine-8.12.0.Alpha3-SNAPSHOT.jar.
This works perfect even when the translator has no support for union.
In the case of when the translator has no support for InlineViews, the ordered limit still doesn't get pushed to the db.
*Query:*
SELECT u.uniqueName, u.majorsubject, u.minorsubject FROM
(select uniqueName, majorsubject, minorsubject, cityid from TESTSCHEMA.student
UNION ALL
select uniqueName, majorsubject, minorsubject, cityid from TESTSCHEMA.student1) as u
LEFT OUTER JOIN TESTSCHEMA.city AS tp ON tp.cityid = u.cityid
where u.uniqueName is null ORDER BY u.uniqueName LIMIT 8
*Plan:*
ProjectNode
+ Relational Node ID:0
+ Output Columns:
0: UNIQUENAME (string)
1: MAJORSUBJECT (string)
2: MINORSUBJECT (string)
+ Statistics:
0: Node Output Rows: 0
1: Node Next Batch Process Time: 0
2: Node Cumulative Next Batch Process Time: 0
3: Node Cumulative Process Time: 0
4: Node Next Batch Calls: 0
5: Node Blocks: 0
+ Cost Estimates:Estimated Node Cardinality: 8.0
+ Child 0:
LimitNode
+ Relational Node ID:1
+ Output Columns:
0: UNIQUENAME (string)
1: MAJORSUBJECT (string)
2: MINORSUBJECT (string)
+ Statistics:
0: Node Output Rows: 0
1: Node Next Batch Process Time: 0
2: Node Cumulative Next Batch Process Time: 0
3: Node Cumulative Process Time: 0
4: Node Next Batch Calls: 0
5: Node Blocks: 0
+ Cost Estimates:Estimated Node Cardinality: 8.0
+ Child 0:
SortNode
+ Relational Node ID:2
+ Output Columns:
0: UNIQUENAME (string)
1: MAJORSUBJECT (string)
2: MINORSUBJECT (string)
+ Statistics:
0: Node Output Rows: 0
1: Node Next Batch Process Time: 0
2: Node Cumulative Next Batch Process Time: 0
3: Node Cumulative Process Time: 0
4: Node Next Batch Calls: 0
5: Node Blocks: 0
+ Cost Estimates:Estimated Node Cardinality: -1.0
+ Child 0:
JoinNode
+ Relational Node ID:3
+ Output Columns:
0: UNIQUENAME (string)
1: MAJORSUBJECT (string)
2: MINORSUBJECT (string)
+ Statistics:
0: Node Output Rows: 0
1: Node Next Batch Process Time: 10
2: Node Cumulative Next Batch Process Time: 20
3: Node Cumulative Process Time: 57
4: Node Next Batch Calls: 2
5: Node Blocks: 1
+ Cost Estimates:Estimated Node Cardinality: -1.0
+ Child 0:
LimitNode
+ Relational Node ID:4
+ Output Columns:
0: CITYID (integer)
1: UNIQUENAME (string)
2: MAJORSUBJECT (string)
3: MINORSUBJECT (string)
+ Statistics:
0: Node Output Rows: 0
1: Node Next Batch Process Time: 0
2: Node Cumulative Next Batch Process Time: 0
3: Node Cumulative Process Time: 0
4: Node Next Batch Calls: 0
5: Node Blocks: 0
+ Cost Estimates:Estimated Node Cardinality: 8.0
+ Child 0:
SortNode
+ Relational Node ID:5
+ Output Columns:
0: CITYID (integer)
1: UNIQUENAME (string)
2: MAJORSUBJECT (string)
3: MINORSUBJECT (string)
+ Statistics:
0: Node Output Rows: 0
1: Node Next Batch Process Time: 0
2: Node Cumulative Next Batch Process Time: 0
3: Node Cumulative Process Time: 0
4: Node Next Batch Calls: 0
5: Node Blocks: 0
+ Cost Estimates:Estimated Node Cardinality: -1.0
+ Child 0:
AccessNode
+ Relational Node ID:6
+ Output Columns:
0: CITYID (integer)
1: UNIQUENAME (string)
2: MAJORSUBJECT (string)
3: MINORSUBJECT (string)
+ Statistics:
0: Node Output Rows: 0
1: Node Next Batch Process Time: 0
2: Node Cumulative Next Batch Process Time: 0
3: Node Cumulative Process Time: 37
4: Node Next Batch Calls: 3
5: Node Blocks: 2
+ Cost Estimates:Estimated Node Cardinality: -1.0
+ Query:SELECT g_1.CITYID AS c_0, g_1.UNIQUENAME AS c_1, g_1.MAJORSUBJECT AS c_2, g_1.MINORSUBJECT AS c_3 FROM actions.ACTIONS.TESTSCHEMA.STUDENT AS g_1 WHERE g_1.UNIQUENAME IS NULL UNION ALL SELECT g_0.CITYID AS c_0, g_0.UNIQUENAME AS c_1, g_0.MAJORSUBJECT AS c_2, g_0.MINORSUBJECT AS c_3 FROM actions.ACTIONS.TESTSCHEMA.STUDENT1 AS g_0 WHERE g_0.UNIQUENAME IS NULL
+ Model Name:actions
+ Sort Columns:[actions.ACTIONS.TESTSCHEMA.STUDENT.UNIQUENAME]
+ Sort Mode:SORT
+ Row Offset:null
+ Row Limit:8
+ Child 1:
AccessNode
+ Relational Node ID:7
+ Output Columns:CITYID (integer)
+ Statistics:
0: Node Output Rows: 0
1: Node Next Batch Process Time: 10
2: Node Cumulative Next Batch Process Time: 10
3: Node Cumulative Process Time: 47
4: Node Next Batch Calls: 2
5: Node Blocks: 1
+ Cost Estimates:Estimated Node Cardinality: -1.0
+ Query:SELECT g_0.CITYID AS c_0 FROM actions.ACTIONS.TESTSCHEMA.CITY AS g_0 ORDER BY c_0
+ Model Name:actions
+ Join Strategy:ENHANCED SORT JOIN RAN AS SORT MERGE (SORT/ALREADY_SORTED)
+ Join Type:LEFT OUTER JOIN
+ Join Criteria:u.CITYID=tp.CITYID
+ Sort Columns:[u.UNIQUENAME]
+ Sort Mode:SORT
+ Row Offset:null
+ Row Limit:8
+ Select Columns:
0: u.UNIQUENAME
1: u.MAJORSUBJECT
2: u.MINORSUBJECT
+ Data Bytes Sent:0
+ Planning Time:80
> Order By and Limit are not getting pushed to the database, when Union and join are used together.
> --------------------------------------------------------------------------------------------------
>
> Key: TEIID-3568
> URL: https://issues.jboss.org/browse/TEIID-3568
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.1
> Reporter: Guru Prasad
> Assignee: Steven Hawkins
> Fix For: 8.12
>
> Attachments: Jars in build path.txt, PushOrderByLimitTest1.java, ShowPlan.txt
>
>
> Order By and Limit are not getting pushed to the database, when Union and join are used together.
> In this scenario there if the underlying table has millions of records the query never returns with data.
> *Query 1*: Using only Join without union, this works fine.
> SELECT u.evttypecode, u.evtsysid, u.evtutctod, u.evtsystod, u.evtcatcode FROM (
> select evttypecode, evtsysid, evtutctod, evtsystod, evtcatcode from XYZ.Tab1
> ) as u
> LEFT OUTER JOIN XYZ.CATEGORY AS ct ON u.evtcatcode = ct.evtcatcode
> WHERE (u.EVTUTCTOD >= {ts'2015-06-03 19:20:00.8'}) AND (u.EVTUTCTOD <= {ts'2015-06-03 19:20:01.0'}) ORDER BY u.evtsysid LIMIT 8
> PROCESSOR PLAN:
> AccessNode(0) output=[evttypecode AS evttypecode, evtsysid AS evtsysid, evtutctod AS evtutctod, evtsystod AS evtsystod, evtcatcode AS evtcatcode]
> SELECT g_0.EVTTYPECODE AS c_0, g_0.EVTSYSID AS c_1, g_0.EVTUTCTOD AS c_2, g_0.EVTSYSTOD AS c_3, g_0.EVTCATCODE AS c_4 FROM ABC.Tab1 AS g_0 LEFT OUTER JOIN ABC.CATEGORY AS g_1 ON g_0.EVTCATCODE = g_1.EVTCATCODE WHERE (g_0.EVTUTCTOD >= {ts'2015-06-03 19:20:00.8'}) AND (g_0.EVTUTCTOD <= {ts'2015-06-03 19:20:01.0'}) ORDER BY c_1 LIMIT 8
> *Query 2*: Using only Union without any join, this also works fine.
> SELECT u.evttypecode, u.evtsysid, u.evtutctod, u.evtsystod, u.evtcatcode FROM (
> select evttypecode, evtsysid, evtutctod, evtsystod, evtcatcode from XYZ.Tab1
> UNION ALL
> select evttypecode, evtsysid, evtutctod, evtsystod, evtcatcode from XYZ.Tab2
> ) as u
> WHERE (u.EVTUTCTOD >= {ts'2015-06-03 19:20:00.8'}) AND (u.EVTUTCTOD <= {ts'2015-06-03 19:20:01.0'}) ORDER BY u.evtsysid LIMIT 8
> PROCESSOR PLAN:
> AccessNode(0) output=[evttypecode AS evttypecode, evtsysid AS evtsysid, evtutctod AS evtutctod, evtsystod AS evtsystod, evtcatcode AS evtcatcode]
> SELECT g_1.EVTTYPECODE AS c_0, g_1.EVTSYSID AS c_1, g_1.EVTUTCTOD AS c_2, g_1.EVTSYSTOD AS c_3, g_1.EVTCATCODE AS c_4 FROM ABC.Tab1 AS g_1 WHERE (g_1.EVTUTCTOD >= {ts'2015-06-03 19:20:00.8'}) AND (g_1.EVTUTCTOD <= {ts'2015-06-03 19:20:01.0'}) UNION ALL
> SELECT g_0.EVTTYPECODE AS c_0, g_0.EVTSYSID AS c_1, g_0.EVTUTCTOD AS c_2, g_0.EVTSYSTOD AS c_3, g_0.EVTCATCODE AS c_4 FROM ABC.Tab2 AS g_0 WHERE (g_0.EVTUTCTOD >= {ts'2015-06-03 19:20:00.8'}) AND (g_0.EVTUTCTOD <= {ts'2015-06-03 19:20:01.0'}) ORDER BY c_1 LIMIT 8
> *Query 3*: Using both Union and join, this does not push down the order by and limit.
> SELECT u.evttypecode, u.evtsysid, u.evtutctod, u.evtsystod, u.evtcatcode FROM (
> select evttypecode, evtsysid, evtutctod, evtsystod, evtcatcode from XYZ.Tab1
> UNION ALL
> select evttypecode, evtsysid, evtutctod, evtsystod, evtcatcode from XYZ.Tab2
> ) as u
> LEFT OUTER JOIN XYZ.EVTTYPE AS tp ON tp.evttypecode = u.evttypecode
> LEFT OUTER JOIN XYZ.CATEGORY AS ct ON u.evtcatcode = ct.evtcatcode
> WHERE (u.EVTUTCTOD >= {ts'2015-06-03 19:20:00.8'}) AND (u.EVTUTCTOD <= {ts'2015-06-03 19:20:01.0'}) ORDER BY u.evtsysid LIMIT 8
> PROCESSOR PLAN:
> ProjectNode(0) output=[u.evttypecode, u.evtsysid, u.evtutctod, u.evtsystod, u.evtcatcode] [u.evttypecode, u.evtsysid, u.evtutctod, u.evtsystod, u.evtcatcode]
> LimitNode(1) output=[u.evttypecode, u.evtsysid, u.evtutctod, u.evtsystod, u.evtcatcode] limit 8
> SortNode(2) output=[u.evttypecode, u.evtsysid, u.evtutctod, u.evtsystod, u.evtcatcode] [SORT] [u.evtsysid]
> JoinNode(3) [MERGE JOIN (SORT/ALREADY_SORTED)] [LEFT OUTER JOIN] criteria=[u.evtcatcode=evtcatcode] output=[u.evttypecode, u.evtsysid, u.evtutctod, u.evtsystod, u.evtcatcode]
> JoinNode(4) [MERGE JOIN (SORT/ALREADY_SORTED)] [LEFT OUTER JOIN] criteria=[u.evttypecode=evttypecode] output=[u.evtcatcode, u.evttypecode, u.evtsysid, u.evtutctod, u.evtsystod]
> AccessNode(5) output=[u.evttypecode, u.evtcatcode, u.evtsysid, u.evtutctod, u.evtsystod]
> SELECT g_1.EVTTYPECODE AS c_0, g_1.EVTCATCODE AS c_1, g_1.EVTSYSID AS c_2, g_1.EVTUTCTOD AS c_3, g_1.EVTSYSTOD AS c_4 FROM ABC.Tab1 AS g_1 WHERE (g_1.EVTUTCTOD >= {ts'2015-06-03 19:20:00.8'}) AND (g_1.EVTUTCTOD <= {ts'2015-06-03 19:20:01.0'})
> UNION ALL SELECT g_0.EVTTYPECODE AS c_0, g_0.EVTCATCODE AS c_1, g_0.EVTSYSID AS c_2, g_0.EVTUTCTOD AS c_3, g_0.EVTSYSTOD AS c_4 FROM ABC.Tab2 AS g_0 WHERE (g_0.EVTUTCTOD >= {ts'2015-06-03 19:20:00.8'}) AND (g_0.EVTUTCTOD <= {ts'2015-06-03 19:20:01.0'})
> AccessNode(6) output=[evttypecode] SELECT g_0.EVTTYPECODE AS c_0 FROM ABC.EVTTYPE AS g_0 ORDER BY c_0
> AccessNode(7) output=[evtcatcode] SELECT g_0.EVTCATCODE AS c_0 FROM ABC.CATEGORY AS g_0 ORDER BY c_0
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3646) Teiid Result Set Caching OPTION NOCACHE problem
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3646?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3646:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1255297
> Teiid Result Set Caching OPTION NOCACHE problem
> -----------------------------------------------
>
> Key: TEIID-3646
> URL: https://issues.jboss.org/browse/TEIID-3646
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> When using 'OPTION NOCACHE' in a query, there are probably still cached results for the query.
> The tested query:
> {code:sql}
> /*+ cache */ SELECT * FROM Customers OPTION NOCACHE
> {code}
> Test scenario:
> Insert value into db, directly through its jdbc driver:
> {code:sql}INSERT INTO Customers VALUES(1, 'name1'){code}
> Check via teiid, that query returns one row. This result set should not be cached.
> {code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code}
> Insert another row into db, via its jdbc driver, not through teiid:
> {code:sql}INSERT INTO Customers VALUES(2, 'name2'){code}
> Check that this query returns again current state of db (2 rows) now:
> {code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code}
> But this check fails, teiid returns only one row, seemingly the result set for query with 'OPTION NOCACHE' gets cached.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3646) Teiid Result Set Caching OPTION NOCACHE problem
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-3646?page=com.atlassian.jira.plugin... ]
Jan Stastny updated TEIID-3646:
-------------------------------
Description:
When using 'OPTION NOCACHE' in a query, there are probably still cached results for the query.
The tested query:
{code:sql}
/*+ cache */ SELECT * FROM Customers OPTION NOCACHE
{code}
Test scenario:
Insert value into db, directly through its jdbc driver:
{code:sql}INSERT INTO Customers VALUES(1, 'name1'){code}
Check via teiid, that query returns one row. This result set should not be cached.
{code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code}
Insert another row into db, via its jdbc driver, not through teiid:
{code:sql}INSERT INTO Customers VALUES(2, 'name2'){code}
Check that this query returns again current state of db (2 rows) now:
{code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code}
But this check fails, teiid returns only one row, seemingly the result set for query with 'OPTION NOCACHE' gets cached.
was:
When using 'OPTION NOCACHE' in a query, there are probably still cached results for the query.
The tested query:
{code:sql}
/*+ cache */ SELECT * FROM Customers OPTION NOCACHE
{code}
Test scenario:
Insert value into db, directly through its jdbc driver:
{code:sql}INSERT INTO Customers VALUES(1, 'name1'){code}
Check via teiid, that query returns one row. This result set should not be cached.
{code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code}
Insert another row into db, via its jdbc driver, not through teiid:
{code:sql}INSERT INTO Customers VALUES(2, 'name2'){code}
Check that this query returns again current state of db (2 rows) now:
{code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code}
But this check fails, teiid returns only one row, seemingly the result set for command with 'OPTION NOCACHE' gets cached.
> Teiid Result Set Caching OPTION NOCACHE problem
> -----------------------------------------------
>
> Key: TEIID-3646
> URL: https://issues.jboss.org/browse/TEIID-3646
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> When using 'OPTION NOCACHE' in a query, there are probably still cached results for the query.
> The tested query:
> {code:sql}
> /*+ cache */ SELECT * FROM Customers OPTION NOCACHE
> {code}
> Test scenario:
> Insert value into db, directly through its jdbc driver:
> {code:sql}INSERT INTO Customers VALUES(1, 'name1'){code}
> Check via teiid, that query returns one row. This result set should not be cached.
> {code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code}
> Insert another row into db, via its jdbc driver, not through teiid:
> {code:sql}INSERT INTO Customers VALUES(2, 'name2'){code}
> Check that this query returns again current state of db (2 rows) now:
> {code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code}
> But this check fails, teiid returns only one row, seemingly the result set for query with 'OPTION NOCACHE' gets cached.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3646) Teiid Result Set Caching OPTION NOCACHE problem
by Jan Stastny (JIRA)
Jan Stastny created TEIID-3646:
----------------------------------
Summary: Teiid Result Set Caching OPTION NOCACHE problem
Key: TEIID-3646
URL: https://issues.jboss.org/browse/TEIID-3646
Project: Teiid
Issue Type: Bug
Affects Versions: 8.7.1.6_2
Reporter: Jan Stastny
Assignee: Steven Hawkins
When using 'OPTION NOCACHE' in a query, there are probably still cached results for the query.
The tested query:
{code:sql}
/*+ cache */ SELECT * FROM Customers OPTION NOCACHE
{code}
Test scenario:
Insert value into db, directly through its jdbc driver:
{code:sql}INSERT INTO Customers VALUES(1, 'name1'){code}
Check via teiid, that query returns one row. This result set should not be cached.
{code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code}
Insert another row into db, via its jdbc driver, not through teiid:
{code:sql}INSERT INTO Customers VALUES(2, 'name2'){code}
Check that this query returns again current state of db (2 rows) now:
{code:sql}/*+ cache */ SELECT * FROM Customers OPTION NOCACHE{code}
But this check fails, teiid returns only one row, seemingly the result set for command with 'OPTION NOCACHE' gets cached.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3645) Upgrade of Amazon aws sdk version
by avinash misra (JIRA)
avinash misra created TEIID-3645:
------------------------------------
Summary: Upgrade of Amazon aws sdk version
Key: TEIID-3645
URL: https://issues.jboss.org/browse/TEIID-3645
Project: Teiid
Issue Type: Component Upgrade
Components: Misc. Connectors
Affects Versions: 8.11.2
Environment: teiid 8.11.2
windows 8.1
java 8
Reporter: avinash misra
Assignee: Steven Hawkins
Fix For: 8.11.3
I was working on dynamodb connector with latest dynamodb sdk.
This sdk uses aws-java-sdk-core version 1.10.11 but teiid uses aws-java-sdk 1.5.7. internally for simple db connector.
Could you please upgrade the aws sdk version to latest?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3538) Make OData V2 compatible with LINQPad
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3538?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3538:
------------------------------------------------
Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1233383|https://bugzilla.redhat.com/show_bug.cgi?id=1233383] from ON_QA to ASSIGNED
> Make OData V2 compatible with LINQPad
> -------------------------------------
>
> Key: TEIID-3538
> URL: https://issues.jboss.org/browse/TEIID-3538
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: Final
> Fix For: 8.7.1.6_2, 8.11
>
> Attachments: $metadata
>
>
> Current OData V2 implementation is not able to load in LINQPad https://www.linqpad.net/
> Couple issues found
> - List(Edm.xxx) based collections are not supported. V2 Spec did not specify any List based collections. Only Collection(Edm.xxx) type. So, part of TEIID-3471 need to be rolled back and fix with Collection(Edm.xxx) type
> - Explicit definition of "not null" in Entity's key property.
> - TEIID-3471 did not go far enough to define accepts header to have "application/xml", "application/atom+xml" and "application/json" without "chaset=utf-8" appended to it. TEIID-3471 only added $metadata and service document. BTW, I was under the impression that I did add all the required places, and was surprised not see in commit :(
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3538) Make OData V2 compatible with LINQPad
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-3538?page=com.atlassian.jira.plugin... ]
Jan Stastny updated TEIID-3538:
-------------------------------
Attachment: $metadata
The $metadata odata description of a vdb
> Make OData V2 compatible with LINQPad
> -------------------------------------
>
> Key: TEIID-3538
> URL: https://issues.jboss.org/browse/TEIID-3538
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: Final
> Fix For: 8.7.1.6_2, 8.11
>
> Attachments: $metadata
>
>
> Current OData V2 implementation is not able to load in LINQPad https://www.linqpad.net/
> Couple issues found
> - List(Edm.xxx) based collections are not supported. V2 Spec did not specify any List based collections. Only Collection(Edm.xxx) type. So, part of TEIID-3471 need to be rolled back and fix with Collection(Edm.xxx) type
> - Explicit definition of "not null" in Entity's key property.
> - TEIID-3471 did not go far enough to define accepts header to have "application/xml", "application/atom+xml" and "application/json" without "chaset=utf-8" appended to it. TEIID-3471 only added $metadata and service document. BTW, I was under the impression that I did add all the required places, and was surprised not see in commit :(
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3538) Make OData V2 compatible with LINQPad
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-3538?page=com.atlassian.jira.plugin... ]
Jan Stastny reopened TEIID-3538:
--------------------------------
I tried with 8.7.1.6_2 and I am not able to create a connection from LINQPad to a vdb. I tried several vdbs. The LINQPad complains about:
{code:plain}"Error: Cannot compile typed context: The namespace 'LINQPad.User' already contains a definition for 'VirtProcs' (line 7268)"{code}
I will also enclose $metadata odata description for the given vdb.
> Make OData V2 compatible with LINQPad
> -------------------------------------
>
> Key: TEIID-3538
> URL: https://issues.jboss.org/browse/TEIID-3538
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: Final
> Fix For: 8.7.1.6_2, 8.11
>
>
> Current OData V2 implementation is not able to load in LINQPad https://www.linqpad.net/
> Couple issues found
> - List(Edm.xxx) based collections are not supported. V2 Spec did not specify any List based collections. Only Collection(Edm.xxx) type. So, part of TEIID-3471 need to be rolled back and fix with Collection(Edm.xxx) type
> - Explicit definition of "not null" in Entity's key property.
> - TEIID-3471 did not go far enough to define accepts header to have "application/xml", "application/atom+xml" and "application/json" without "chaset=utf-8" appended to it. TEIID-3471 only added $metadata and service document. BTW, I was under the impression that I did add all the required places, and was surprised not see in commit :(
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3625) JDG translator has disabled capabilities for GT and LT
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3625?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3625:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1252914|https://bugzilla.redhat.com/show_bug.cgi?id=1252914] from NEW to MODIFIED
> JDG translator has disabled capabilities for GT and LT
> ------------------------------------------------------
>
> Key: TEIID-3625
> URL: https://issues.jboss.org/browse/TEIID-3625
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Filip Elias
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> Operations GT and LT are not pushed down to JDG. Indexes are enabled for all columns. Operations GE and LE are pushed down correctly.
> Example:
> The first query is pushed down correctly. The second query doesn't push the "greater than" operator to the source.
> Query:
> {code}select intkey from smalla where intNum >= 5 order by intkey{code}
> PROCESSOR PLAN:
> {code}
> AccessNode(0) output=[c.intKey AS IntKey] SELECT g_0.intKey FROM SmallAs.smallARemotecache AS g_0 WHERE g_0.intNum >= 5 ORDER BY g_0.intKey
> {code}
> Query:
> {code}select intkey from smalla where intNum > 5 order by intkey{code}
> Plan:
> {code}
> SortNode(0) output=[c.intKey AS IntKey] [SORT] [IntKey]
> ProjectNode(1) output=[c.intKey AS IntKey] [c.intKey AS IntKey]
> SelectNode(2) output=[c.intKey] c.intNum > 5
> AccessNode(3) output=[c.intNum, c.intKey] SELECT g_0.intNum, g_0.intKey FROM SmallAs.smallARemotecache AS g_0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months