[JBoss JIRA] (TEIID-2503) XML Recursive and Nested Doc queries are producing "TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error"
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2503?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2503.
-----------------------------------
Fix Version/s: (was: 8.4.1)
Resolution: Rejected
This is using a staging table with an input set. As far as I know that hasn't been supported in years and to confirm 7.7 also exhibits the same exception. This is something that could be brought backing with customer need (assuming that support can be resurrected in Designer).…
[View More]
> XML Recursive and Nested Doc queries are producing "TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error"
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2503
> URL: https://issues.jboss.org/browse/TEIID-2503
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.4
> Environment: EAP6.1Alpha and Teiid8.4Alpha
> Reporter: Warren Gibson
> Assignee: Steven Hawkins
> Priority: Minor
> Attachments: QT_PostgreSQL91_Push.vdb, SERVER.log
>
>
> The following queries are producing TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error.
> The queries were returning expected query results in SOA-P5.3.1 release. However, when testing them with EAP 6.1Alpha and
> Teiid 8.4Alpha they are returning the "Unable to evaluate "INPUT".nextKey" message. This is occuring on Postgres91, Oracle10,11,11RAC, Mysql55, Teradata, and Greenplum data sources.
> I isolated "SELECT * FROM XQTNestedDoc.testSimpleNested ORDER BY recursiveroot.key" and ran a test to produce a log entry which
> is attached. If you need other testing artifacts such as VDB please let me know.
> SELECT * FROM XQTNestedDoc.testBoundTempTable
> SELECT * FROM XQTNestedDoc.testExcludeFromDoc ORDER BY recursiveroot.key
> SELECT * FROM XQTNestedDoc.testOptimizableTempTable ORDER BY recursiveroot.key
> SELECT * FROM XQTNestedDoc.testRootTempTable ORDER BY recursiveroot.key
> SELECT * FROM XQTNestedDoc.testSimpleNested ORDER BY recursiveroot.key
> SELECT * FROM XQTRecursiveDoc.testNested2Document ORDER BY recursiveroot.key
> SELECT * FROM XQTRecursiveDoc.testNestedDocument ORDER BY recursiveroot.key
> SELECT * FROM XQTRecursiveDoc.testSimpleDocument ORDER BY recursiveroot.key
> SELECT * FROM XQTRecursiveDoc.testSimpleTempTable ORDER BY recursiveroot.key
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 8 months
[JBoss JIRA] (TEIID-2522) Let Extract(<Oracle Date field>) extract time components
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2522?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2522:
----------------------------------
Issue Type: Enhancement (was: Feature Request)
Priority: Minor (was: Major)
Component/s: JDBC Connector
> Let Extract(<Oracle Date field>) extract time components
> --------------------------------------------------------
>
> Key: TEIID-2522
> URL: https://issues.jboss.…
[View More]org/browse/TEIID-2522
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Connector
> Reporter: Alex K.
> Assignee: Steven Hawkins
> Priority: Minor
>
> According to the Oracle's docs:
>
> "The DATE datatype stores point-in-time values (dates and times) in a table. The DATE datatype stores the year (including the century), the month, the day, the hours, the minutes, and the seconds (after midnight)."
>
> I expect to be able to extract the time parts from a date field, but when I am trying to extract the hour from an oracle's date field like:
>
> {code:sql}
> SELECT EXTRACT(HOUR FROM a.modifieddate)
> FROM oracle_db.salestaxrate a
> WHERE a.salestaxrateid = 1
> {code}
>
> and get a TEIID30504 exception. When I look deeper in Teiid's log, i see the following Oracle's exception:
>
> Caused by: java.sql.SQLException: Remote java.sql.SQLException: ORA-30076: invalid extract field for extract source
> That is an odd Oracle limitation - http://docs.oracle.com/cd/B28359_01/server.111/b28286/functions052.htm
>
> "If HOUR, MINUTE, or SECOND is requested, then expr must evaluate to an expression of datatype TIMESTAMP, TIMESTAMP WITH TIME ZONE, TIMESTAMP WITH LOCAL TIME ZONE, or INTERVAL DAY TO SECOND. DATE is not valid here, because Oracle Database treats it as ANSI DATE datatype, which has no time fields."
> *please enable extracting of time components from oracle's Date Fields* despite the Oracle's limitation
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 8 months
[JBoss JIRA] (TEIID-2519) Odata Table Query Not Workng
by devin pinkston (JIRA)
[ https://issues.jboss.org/browse/TEIID-2519?page=com.atlassian.jira.plugin... ]
devin pinkston commented on TEIID-2519:
---------------------------------------
Ramesh,
I moved all the resource adapters/connections over to 8.4 CR1 with JBOSS EAP. All is up and working, VDB is deployed and active.
Still receiving same status however when trying to access data through Odata. If i connect through Squirrel i can still see my tables and access them.
I'm really not sure what it could be? …
[View More]Perhaps I have something off in my configuration? However it is the same as before.
Thank you
> Odata Table Query Not Workng
> ----------------------------
>
> Key: TEIID-2519
> URL: https://issues.jboss.org/browse/TEIID-2519
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.3
> Environment: CentOS, JBOSS AS 7.1.1, Teiid 8.3.
> Reporter: devin pinkston
> Assignee: Ramesh Reddy
> Priority: Minor
> Labels: odata,, service,, web
> Fix For: 8.4
>
> Attachments: metadata.txt, portfolio-vdb.xml, portfolio-vdb.xml
>
>
> When trying to query a table through Odata, a error is diplayed: EdmEntitySet refinedSalariesModel.refinedSalaries is not found
> When issuing the query:
> http://localhost:8080/odata/Portfolio.1/refinedSalariesModel.refinedSalaries
> We have also tried using:
> http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries
> When issuing the second query, this error is thrown:
> <error><code/><message lang="en-US">Could not find resource for relative : /refinedSalariesModel/refinedSalaries of full path: http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries</message></error>
> We can successfully display the metadata and see the details of the VDB by using:
> http://localhost:8080/odata/Portfolio.1/$metadata
> Please let me know if you need any more information
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 8 months
[JBoss JIRA] (TEIID-2522) Let Extract(<Oracle Date field>) extract time components
by Alex K. (JIRA)
Alex K. created TEIID-2522:
------------------------------
Summary: Let Extract(<Oracle Date field>) extract time components
Key: TEIID-2522
URL: https://issues.jboss.org/browse/TEIID-2522
Project: Teiid
Issue Type: Feature Request
Reporter: Alex K.
Assignee: Steven Hawkins
According to the Oracle's docs:
"The DATE datatype stores point-in-time values (dates and times) in a table. The DATE …
[View More]datatype stores the year (including the century), the month, the day, the hours, the minutes, and the seconds (after midnight)."
I expect to be able to extract the time parts from a date field, but when I am trying to extract the hour from an oracle's date field like:
{code:sql}
SELECT EXTRACT(HOUR FROM a.modifieddate)
FROM oracle_db.salestaxrate a
WHERE a.salestaxrateid = 1
{code}
and get a TEIID30504 exception. When I look deeper in Teiid's log, i see the following Oracle's exception:
Caused by: java.sql.SQLException: Remote java.sql.SQLException: ORA-30076: invalid extract field for extract source
That is an odd Oracle limitation - http://docs.oracle.com/cd/B28359_01/server.111/b28286/functions052.htm
"If HOUR, MINUTE, or SECOND is requested, then expr must evaluate to an expression of datatype TIMESTAMP, TIMESTAMP WITH TIME ZONE, TIMESTAMP WITH LOCAL TIME ZONE, or INTERVAL DAY TO SECOND. DATE is not valid here, because Oracle Database treats it as ANSI DATE datatype, which has no time fields."
*please enable extracting of time components from oracle's Date Fields* despite the Oracle's limitation
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 8 months
[JBoss JIRA] (TEIID-2519) Odata Table Query Not Workng
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2519?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2519:
-------------------------------------
I went back and tested with Teiid 8.3.Beta3 it works, with Final I see the behavior you are seeing. Seems like a regression, not sure what that is yet?
I tried with 8.4.CR1 it works as expected, can you test/move to the latest and make sure it works for your usecase before 8.4 Final?
> Odata Table Query Not Workng
&…
[View More]gt; ----------------------------
>
> Key: TEIID-2519
> URL: https://issues.jboss.org/browse/TEIID-2519
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.3
> Environment: CentOS, JBOSS AS 7.1.1, Teiid 8.3.
> Reporter: devin pinkston
> Assignee: Ramesh Reddy
> Priority: Minor
> Labels: odata,, service,, web
> Fix For: 8.4
>
> Attachments: metadata.txt, portfolio-vdb.xml, portfolio-vdb.xml
>
>
> When trying to query a table through Odata, a error is diplayed: EdmEntitySet refinedSalariesModel.refinedSalaries is not found
> When issuing the query:
> http://localhost:8080/odata/Portfolio.1/refinedSalariesModel.refinedSalaries
> We have also tried using:
> http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries
> When issuing the second query, this error is thrown:
> <error><code/><message lang="en-US">Could not find resource for relative : /refinedSalariesModel/refinedSalaries of full path: http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries</message></error>
> We can successfully display the metadata and see the details of the VDB by using:
> http://localhost:8080/odata/Portfolio.1/$metadata
> Please let me know if you need any more information
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 8 months
[JBoss JIRA] (TEIID-2519) Odata Table Query Not Workng
by devin pinkston (JIRA)
[ https://issues.jboss.org/browse/TEIID-2519?page=com.atlassian.jira.plugin... ]
devin pinkston commented on TEIID-2519:
---------------------------------------
Ramesh,
I tried your VDB and I still receive: <error><code>NotFoundException</code><message lang="en-US">EdmEntitySet MarketData.G1 is not found</message></error>
I can see my VDB deployed and active too! Could it have something to do with that I have Teiid running on a server? However I pass …
[View More]in the correct ip address when starting.
And with my other VDB i have been using, I can issue queries from tables and receive accurate results!
Any ideas? Thanks for your time!
> Odata Table Query Not Workng
> ----------------------------
>
> Key: TEIID-2519
> URL: https://issues.jboss.org/browse/TEIID-2519
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.3
> Environment: CentOS, JBOSS AS 7.1.1, Teiid 8.3.
> Reporter: devin pinkston
> Assignee: Ramesh Reddy
> Priority: Minor
> Labels: odata,, service,, web
> Fix For: 8.4
>
> Attachments: metadata.txt, portfolio-vdb.xml, portfolio-vdb.xml
>
>
> When trying to query a table through Odata, a error is diplayed: EdmEntitySet refinedSalariesModel.refinedSalaries is not found
> When issuing the query:
> http://localhost:8080/odata/Portfolio.1/refinedSalariesModel.refinedSalaries
> We have also tried using:
> http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries
> When issuing the second query, this error is thrown:
> <error><code/><message lang="en-US">Could not find resource for relative : /refinedSalariesModel/refinedSalaries of full path: http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries</message></error>
> We can successfully display the metadata and see the details of the VDB by using:
> http://localhost:8080/odata/Portfolio.1/$metadata
> Please let me know if you need any more information
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 8 months