[JBoss JIRA] (TEIID-5896) enable EXTRACT EPOCH/QUARTER from timestamp
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5896?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5896.
-----------------------------------
Resolution: Done
Added the extract targets for quarter and epoch. We already supported a quarter function, so that didn't require any additional changes. An epoch function was added to support microsecond precision (the same as pg and double won't support all the way to nanoseconds).
> enable EXTRACT EPOCH/QUARTER from timestamp
> -------------------------------------------
>
> Key: TEIID-5896
> URL: https://issues.redhat.com/browse/TEIID-5896
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar
> Affects Versions: 12.3.1
> Reporter: Ken Geis
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.1
>
>
> I am connecting to Teiid from Tableau using the JDBC driver and PostgreSQL dialect. I try to drill into a timestamp field, and I get some complaints parsing the SQL. In particular, it has trouble with:
> {code:java}
> EXTRACT(QUARTER FROM the_time)
> EXTRACT(EPOCH FROM the_time)
> {code}
> The docs suggest these datetime components are not supported by Teiid. They are not standard, but supporting them would get me a step closer to running Tableau against Teiid (a killer app!)
> I was able to work around the QUARTER by dismissing the error, drilling down to month, dismissing the error again, then dragging the quarter out of my drill-down.
> I worked around the EPOCH by moving a date difference from being calculated in Tableau to calculating it in Teiid with TIMESTAMPDIFF.
> An alternate I tried was using Tableau's SQL92 dialect, but it issues a "SELECT TOP" clause that is not SQL92 standard and also not supported by Teiid.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (TEIID-5896) enable EXTRACT EPOCH/QUARTER from timestamp
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5896?page=com.atlassian.jira.plugi... ]
Work on TEIID-5896 started by Steven Hawkins.
---------------------------------------------
> enable EXTRACT EPOCH/QUARTER from timestamp
> -------------------------------------------
>
> Key: TEIID-5896
> URL: https://issues.redhat.com/browse/TEIID-5896
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar
> Affects Versions: 12.3.1
> Reporter: Ken Geis
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.1
>
>
> I am connecting to Teiid from Tableau using the JDBC driver and PostgreSQL dialect. I try to drill into a timestamp field, and I get some complaints parsing the SQL. In particular, it has trouble with:
> {code:java}
> EXTRACT(QUARTER FROM the_time)
> EXTRACT(EPOCH FROM the_time)
> {code}
> The docs suggest these datetime components are not supported by Teiid. They are not standard, but supporting them would get me a step closer to running Tableau against Teiid (a killer app!)
> I was able to work around the QUARTER by dismissing the error, drilling down to month, dismissing the error again, then dragging the quarter out of my drill-down.
> I worked around the EPOCH by moving a date difference from being calculated in Tableau to calculating it in Teiid with TIMESTAMPDIFF.
> An alternate I tried was using Tableau's SQL92 dialect, but it issues a "SELECT TOP" clause that is not SQL92 standard and also not supported by Teiid.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (TEIID-5896) enable EXTRACT EPOCH/QUARTER from timestamp
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5896?page=com.atlassian.jira.plugi... ]
Steven Hawkins reassigned TEIID-5896:
-------------------------------------
Assignee: Steven Hawkins (was: Barry LaFond)
> enable EXTRACT EPOCH/QUARTER from timestamp
> -------------------------------------------
>
> Key: TEIID-5896
> URL: https://issues.redhat.com/browse/TEIID-5896
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar
> Affects Versions: 12.3.1
> Reporter: Ken Geis
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.1
>
>
> I am connecting to Teiid from Tableau using the JDBC driver and PostgreSQL dialect. I try to drill into a timestamp field, and I get some complaints parsing the SQL. In particular, it has trouble with:
> {code:java}
> EXTRACT(QUARTER FROM the_time)
> EXTRACT(EPOCH FROM the_time)
> {code}
> The docs suggest these datetime components are not supported by Teiid. They are not standard, but supporting them would get me a step closer to running Tableau against Teiid (a killer app!)
> I was able to work around the QUARTER by dismissing the error, drilling down to month, dismissing the error again, then dragging the quarter out of my drill-down.
> I worked around the EPOCH by moving a date difference from being calculated in Tableau to calculating it in Teiid with TIMESTAMPDIFF.
> An alternate I tried was using Tableau's SQL92 dialect, but it issues a "SELECT TOP" clause that is not SQL92 standard and also not supported by Teiid.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (TEIID-5896) enable EXTRACT EPOCH/QUARTER from timestamp
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5896?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5896:
----------------------------------
Fix Version/s: 13.1
Sprint: DV Sprint 59
> enable EXTRACT EPOCH/QUARTER from timestamp
> -------------------------------------------
>
> Key: TEIID-5896
> URL: https://issues.redhat.com/browse/TEIID-5896
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar
> Affects Versions: 12.3.1
> Reporter: Ken Geis
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.1
>
>
> I am connecting to Teiid from Tableau using the JDBC driver and PostgreSQL dialect. I try to drill into a timestamp field, and I get some complaints parsing the SQL. In particular, it has trouble with:
> {code:java}
> EXTRACT(QUARTER FROM the_time)
> EXTRACT(EPOCH FROM the_time)
> {code}
> The docs suggest these datetime components are not supported by Teiid. They are not standard, but supporting them would get me a step closer to running Tableau against Teiid (a killer app!)
> I was able to work around the QUARTER by dismissing the error, drilling down to month, dismissing the error again, then dragging the quarter out of my drill-down.
> I worked around the EPOCH by moving a date difference from being calculated in Tableau to calculating it in Teiid with TIMESTAMPDIFF.
> An alternate I tried was using Tableau's SQL92 dialect, but it issues a "SELECT TOP" clause that is not SQL92 standard and also not supported by Teiid.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (TEIID-5846) Support "order by" by default in the salesforce translator
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5846?page=com.atlassian.jira.plugi... ]
Work on TEIID-5846 started by Steven Hawkins.
---------------------------------------------
> Support "order by" by default in the salesforce translator
> ----------------------------------------------------------
>
> Key: TEIID-5846
> URL: https://issues.redhat.com/browse/TEIID-5846
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Environment: teiid-spring-boot+spring-odata teiid+spring-data-salesforce
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.1
>
>
> When we call simple request as
> salesforce-odata-facade/odata/salesforce/Product_License__c?$top=1&$select=Id
> request processing time is 1min. But this request processing by simple SOAP SOQL request is ~150ms.
> I think this do because teiid select all objects by ignoring top in request.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (TEIID-5527) show plan over pg protocol needs some thought
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5527?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5527.
-----------------------------------
Fix Version/s: (was: 13.x)
Resolution: Duplicate Issue
Duplicate of TEIID-5740
> show plan over pg protocol needs some thought
> ---------------------------------------------
>
> Key: TEIID-5527
> URL: https://issues.redhat.com/browse/TEIID-5527
> Project: Teiid
> Issue Type: Quality Risk
> Components: ODBC
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
>
> Depending upon the client and the particulars of processing - simple or extended query protocol - issuing a show plan may not give the relevant plan. For example if you obtain a resultset using the jdbc client and a simple query has been issued, a show plan at the end of processing will actually show some of the under the covers metadata queries.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (TEIID-5860) Salesforce translator should support self joins
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5860?page=com.atlassian.jira.plugi... ]
Work on TEIID-5860 started by Steven Hawkins.
---------------------------------------------
> Salesforce translator should support self joins
> -----------------------------------------------
>
> Key: TEIID-5860
> URL: https://issues.redhat.com/browse/TEIID-5860
> Project: Teiid
> Issue Type: Enhancement
> Components: Salesforce Connector
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.1
>
>
> In this query
> {code}
> SELECT originalLicense.Id,originalLicense.Status__c,originalLicense.ReplacementLicenseID__c,originalLicense.LicenseId__c,originalLicense.vlic_Contract_Number__c,replacementLicense.LicenseId__c as replacementLicenseId ,replacementLicense.LicenseId__c as replacementLicenseLicenseId FROM Product_License__c originalLicense LEFT OUTER JOIN /*+ MAKEDEP */ Product_License__c replacementLicense ON originalLicense.ReplacementLicenseID__c = replacementLicense.Id where originalLicense.vlic_Contract_Number__c = :contractNumber
> {code}
> We have two requests to salesforce, but could generate a single SOQL query.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (TEIID-5610) XML parsing from web service error (TEIID30151)
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5610?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5610.
-----------------------------------
Fix Version/s: (was: 13.x)
Resolution: Out of Date
Please use JSONTABLE / JSONPATH - TEIID-5481
> XML parsing from web service error (TEIID30151)
> -----------------------------------------------
>
> Key: TEIID-5610
> URL: https://issues.redhat.com/browse/TEIID-5610
> Project: Teiid
> Issue Type: Bug
> Components: VDB
> Affects Versions: 10.2
> Environment: Create teiid VDB containing 1 Oracle source and 1 REST service source. Define REST service like this:
> CREATE VIRTUAL PROCEDURE WS_PROCEDURE(SEARCH_INPUT varchar) RETURNS (
> FILE_ID varchar,
> FILE_NAME string
> )
> AS
> SELECT
> A.FILE_ID, A.FILE_NAME
> FROM
> (
> EXEC MY_WS.INVOKEHTTP(
> ...
> )
> ) AS F,
> XMLTABLE(
> '/myxml/response/docs' PASSING JSONTOXML('myxml', F.RESULT) COLUMNS
> FILE_ID string PATH 'fileid',
> FILE_NAME string PATH 'filename'
> )
> AS A;
> CREATE VIEW WS_VIEW AS SELECT * FROM REST_WS.WS_PROCEDURE;
> Reporter: Andreas Krück
> Assignee: Steven Hawkins
> Priority: Major
>
> After TEIID-5294 has been fixed, we are still facing issues after an update to v10.2. Error message "TEIID30151 Error building Source for context item" when calling SQL statement on VDB connected to REST service:
> 09:15:44,117 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2475) Request Thread Fk5ykF/8Bdl6.15 - processor blocked
> 09:15:44,539 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2478) Request Thread Ri4uuB5w1vOK.35 with state PROCESSING
> 09:15:44,539 DEBUG [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue2479) Using stream processing for evaluation of /myxml/response/docs
> 09:15:44,555 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2478) QueryProcessor: closing processor
> 09:15:44,555 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2478) QueryProcessor: closing processor
> 09:15:44,555 DEBUG [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue2480) Running task for parent thread Worker15_QueryProcessorQueue2478
> 09:15:44,555 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2478) Request Thread Ri4uuB5w1vOK.35 - processor blocked
> 09:15:45,211 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2481) Request Thread Fk5ykF/8Bdl6.15 with state PROCESSING
> 09:15:45,211 DEBUG [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue2482) Using stream processing for evaluation of /myxml/response/docs
> 09:15:45,211 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2481) QueryProcessor: closing processor
> 09:15:45,211 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2481) Created intermediate sort buffer 1570
> 09:15:45,211 DEBUG [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue2483) Running task for parent thread Worker15_QueryProcessorQueue2481
> 09:15:45,211 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2481) Request Thread Fk5ykF/8Bdl6.15 - processor blocked
> 09:15:45,367 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2484) Request Thread Fk5ykF/8Bdl6.15 with state PROCESSING
> 09:15:45,367 DEBUG [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue2485) Using stream processing for evaluation of /myxml/response
> 09:15:45,367 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2484) QueryProcessor: closing processor
> 09:15:45,367 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2484) QueryProcessor: closing processor
> 09:15:45,367 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2484) QueryProcessor: closing processor
> 09:15:45,383 WARN [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2484) TEIID30020 Processing exception for request Fk5ykF/8Bdl6.15 'TEIID30151 Error building Source for context item.'. Originally TeiidProcessingException '0xb is not allowed in XML content' nu.xom.Verifier.throwIllegalCharacterDataException(Unknown Source).: org.teiid.core.TeiidProcessingException: TEIID30151 Error building Source for context item.
> at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:174)
> at org.teiid.query.processor.relational.XMLTableNode$1.run(XMLTableNode.java:266)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:277)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: nu.xom.ParsingException: 0xb is not allowed in XML content
> at nu.xom.Builder.build(Unknown Source)
> at nu.xom.Builder.build(Unknown Source)
> at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:168)
> ... 7 more
> Caused by: nu.xom.IllegalCharacterDataException: 0xb is not allowed in XML content
> at nu.xom.Verifier.throwIllegalCharacterDataException(Unknown Source)
> at nu.xom.Verifier.checkPCDATA(Unknown Source)
> at nu.xom.Text._setValue(Unknown Source)
> at nu.xom.Text.<init>(Unknown Source)
> at nu.xom.NodeFactory.makeText(Unknown Source)
> at nux.xom.pool.XOMUtil$1.makeText(XOMUtil.java:92)
> at nux.xom.xquery.StreamingPathFilter$StreamingPathFilterNodeFactory.makeText(StreamingPathFilter.java:492)
> at nu.xom.XOMHandler.flushText(Unknown Source)
> at nu.xom.XOMHandler.endElement(Unknown Source)
> at net.sf.saxon.event.ContentHandlerProxy.endElement(ContentHandlerProxy.java:414)
> at org.teiid.query.xquery.saxon.ContentHandlerProxyReceiver.endElement(StreamingUtils.java:258)
> at net.sf.saxon.event.ProxyReceiver.endElement(ProxyReceiver.java:182)
> at org.teiid.query.xquery.saxon.PathMapFilter.endElement(PathMapFilter.java:219)
> at net.sf.saxon.pull.PullPushTee.copyEvent(PullPushTee.java:134)
> at net.sf.saxon.pull.PullPushTee.next(PullPushTee.java:72)
> at net.sf.saxon.pull.PullConsumer.consume(PullConsumer.java:42)
> at net.sf.saxon.pull.PullPushCopier.copy(PullPushCopier.java:44)
> at net.sf.saxon.event.Sender.sendPullSource(Sender.java:520)
> at net.sf.saxon.event.Sender.send(Sender.java:182)
> at net.sf.saxon.Configuration.buildDocumentTree(Configuration.java:4032)
> at net.sf.saxon.Configuration.buildDocumentTree(Configuration.java:3970)
> at org.teiid.query.xquery.saxon.SaxonReader.parse(StreamingUtils.java:176)
> ... 10 more
>
> 09:15:45,383 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2484) Removing tuplesource for the request Fk5ykF/8Bdl6.15
> 09:15:45,383 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2484) Fk5ykF/8Bdl6.15 Finished Processing
> 09:15:45,383 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2484) org.teiid.core.TeiidProcessingException: TEIID30151 Error building Source for context item. Sending error to client Fk5ykF/8Bdl6.15
> 09:15:45,430 DEBUG [org.teiid.PROCESSOR] (NIO6) closeQuery for requestID=Fk5ykF/8Bdl6.13
> 09:15:45,430 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2486) Request Thread Fk5ykF/8Bdl6.13 with state CLOSE
> 09:15:45,430 DEBUG [org.teiid.PROCESSOR] (Worker15_QueryProcessorQueue2486) Removing tuplesource for the request Fk5ykF/8Bdl6.13
> 09:15:45,430 DEBUG [org.teiid.PROCESSOR] (NIO6) closeQuery for requestID=Fk5ykF/8Bdl6.14
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months