[JBoss JIRA] (TEIID-4224) HANA translator : incorrect pushdown of DAYOFWEEK function
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4224?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4224:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1339611
Bugzilla Update: Perform
> HANA translator : incorrect pushdown of DAYOFWEEK function
> ----------------------------------------------------------
>
> Key: TEIID-4224
> URL: https://issues.jboss.org/browse/TEIID-4224
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.5
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> Teiid's DAYOFWEEK function:
> {code:plain}
> DAYOFWEEK(x) Return day of week (Sunday=1, Saturday=7)
> {code}
> is pushed down as:
> {code:plain}
> dayname(g_0."DATEVALUE")
> {code}
> but this function returns string representation of the day.
> More appropriate would be to push DAYOFWEEK as WEEKDAY function, but the returned value has to be adapted to Teiid's representation (Sunday=1 and Saturday=7, vs. HANA's Monday=0,Sunday=6). So the solution would be to push:
> {code:sql}
> MOD((WEEKDAY(datevalue)+1),7)+1
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4224) HANA translator : incorrect pushdown of DAYOFWEEK function
by Jan Stastny (JIRA)
Jan Stastny created TEIID-4224:
----------------------------------
Summary: HANA translator : incorrect pushdown of DAYOFWEEK function
Key: TEIID-4224
URL: https://issues.jboss.org/browse/TEIID-4224
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.5
Reporter: Jan Stastny
Assignee: Steven Hawkins
Teiid's DAYOFWEEK function:
{code:plain}
DAYOFWEEK(x) Return day of week (Sunday=1, Saturday=7)
{code}
is pushed down as:
{code:plain}
dayname(g_0."DATEVALUE")
{code}
but this function returns string representation of the day.
More appropriate would be to push DAYOFWEEK as WEEKDAY function, but the returned value has to be adapted to Teiid's representation (Sunday=1 and Saturday=7, vs. HANA's Monday=0,Sunday=6). So the solution would be to push:
{code:sql}
MOD((WEEKDAY(datevalue)+1),7)+1
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4207) Limit pushdown is incorrect for simpledb
by Tugba Dogan (JIRA)
[ https://issues.jboss.org/browse/TEIID-4207?page=com.atlassian.jira.plugin... ]
Tugba Dogan commented on TEIID-4207:
------------------------------------
I checked the connector's source code.There are 2 options to solve this issue:
* We can remove the limit support by removing the following lines.
{code:java}
@Override
public boolean supportsRowLimit() {
return true;
}
{code}
{code:java}
if (!useSelectLimit() && obj.getLimit() != null) {
buffer.append(Tokens.SPACE);
append(obj.getLimit());
}
{code}
* We don't know how many rows will be in each page so we can count the retrieved rows and we can return limited rows.
> Limit pushdown is incorrect for simpledb
> ----------------------------------------
>
> Key: TEIID-4207
> URL: https://issues.jboss.org/browse/TEIID-4207
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Tugba Dogan
> Fix For: 9.0, 8.12.5, 8.13.5
>
>
> The limit clause for simpledb sets a page size rather than fully limiting results, thus our pushdown is incorrect.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4207) Limit pushdown is incorrect for simpledb
by Tugba Dogan (JIRA)
[ https://issues.jboss.org/browse/TEIID-4207?page=com.atlassian.jira.plugin... ]
Tugba Dogan edited comment on TEIID-4207 at 5/25/16 8:08 AM:
-------------------------------------------------------------
I checked the connector's source code.There are 2 options to solve this issue:
* We can remove the limit support by removing the following lines.
{code:java}
@Override
public boolean supportsRowLimit() {
return true;
}
{code}
{code:java}
if (!useSelectLimit() && obj.getLimit() != null) {
buffer.append(Tokens.SPACE);
append(obj.getLimit());
}
{code}
* We don't know how many rows will be in each page so we can count the retrieved rows and we can return limited rows.
was (Author: tugbadogan):
I checked the connector's source code.There are 2 options to solve this issue:
* We can remove the limit support by removing the following lines.
{code:java}
@Override
public boolean supportsRowLimit() {
return true;
}
{code}
{code:java}
if (!useSelectLimit() && obj.getLimit() != null) {
buffer.append(Tokens.SPACE);
append(obj.getLimit());
}
{code}
* We don't know how many rows will be in each page so we can count the retrieved rows and we can return limited rows.
> Limit pushdown is incorrect for simpledb
> ----------------------------------------
>
> Key: TEIID-4207
> URL: https://issues.jboss.org/browse/TEIID-4207
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Tugba Dogan
> Fix For: 9.0, 8.12.5, 8.13.5
>
>
> The limit clause for simpledb sets a page size rather than fully limiting results, thus our pushdown is incorrect.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4223) Hana translator: incorrect pushdown of QUARTER function
by Jan Stastny (JIRA)
Jan Stastny created TEIID-4223:
----------------------------------
Summary: Hana translator: incorrect pushdown of QUARTER function
Key: TEIID-4223
URL: https://issues.jboss.org/browse/TEIID-4223
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.5
Reporter: Jan Stastny
Assignee: Steven Hawkins
Teiid's QUARTER function returns integer.
SAP HANA's QUARTER function returns string in form:
{code:plain}
2000-Q1
{code}
So the function either shouldn't be pushed down, or it has to be pushed down together with some substring method wrapping it:
{code:sql}
SUBSTR_REGEXPR('[[:digit:]]{4}\-Q([[:digit:]]{1})' IN quarter(datevalue) GROUP 1)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4221) HANA translator: incorrect pushdown of week function
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4221?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4221:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1339568
Bugzilla Update: Perform
> HANA translator: incorrect pushdown of week function
> ----------------------------------------------------
>
> Key: TEIID-4221
> URL: https://issues.jboss.org/browse/TEIID-4221
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.5
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> Hana translator pushes down function week to SAP HANA datasource as its WEEK function. But it is not in accordance with the ISO8601 rule.
> For this standard, HANA has function ISOWEEK, which returns results in following format:
> {code:plain}
> 2000-W01 for date 'Jan 3, 2000'
> {code}
> So it should be possible to push Teiid's WEEK function as:
> {code:sql}
> SUBSTR_REGEXPR('[[:digit:]]{4}\-W([[:digit:]]{2})' IN ISOWEEK(datevalue) GROUP 1)
> {code}
> where 'datevalue' is column of DATE datatype.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4222) replace JBoss AS to WildFly
by Kylin Soong (JIRA)
Kylin Soong created TEIID-4222:
----------------------------------
Summary: replace JBoss AS to WildFly
Key: TEIID-4222
URL: https://issues.jboss.org/browse/TEIID-4222
Project: Teiid
Issue Type: Sub-task
Components: Documentation
Affects Versions: 9.x
Reporter: Kylin Soong
Assignee: Kylin Soong
Fix For: 9.x
There are lots of place depict server as "JBoss AS", but start from 8.13, server is "WildFly".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4221) HANA translator: incorrect pushdown of week function
by Jan Stastny (JIRA)
Jan Stastny created TEIID-4221:
----------------------------------
Summary: HANA translator: incorrect pushdown of week function
Key: TEIID-4221
URL: https://issues.jboss.org/browse/TEIID-4221
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.5
Reporter: Jan Stastny
Assignee: Steven Hawkins
Hana translator pushes down function week to SAP HANA datasource as its WEEK function. But it is not in accordance with the ISO8601 rule.
For this standard, HANA has function ISOWEEK, which returns results in following format:
{code:plain}
2000-W01 for date 'Jan 3, 2000'
{code}
So it should be possible to push Teiid's WEEK function as:
{code:sql}
SUBSTR_REGEXPR('[[:digit:]]{4}\-W([[:digit:]]{2})' IN ISOWEEK(datevalue) GROUP 1)
{code}
where 'datevalue' is column of DATE datatype.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4220) Unsupported encoding when POSTing to odata on Windows
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIID-4220:
-------------------------------------
Summary: Unsupported encoding when POSTing to odata on Windows
Key: TEIID-4220
URL: https://issues.jboss.org/browse/TEIID-4220
Project: Teiid
Issue Type: Bug
Components: OData
Affects Versions: 8.12.x
Reporter: Andrej Šmigala
Assignee: Steven Hawkins
Priority: Critical
When posting to a windows server from a windows client, the default encoding is cp1252. When an xml request such as this is posted:
{code:xml}
<?xml version='1.0' encoding='cp1252'?><entry xmlns="http://www.w3.org/2005/Atom" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:m="http://docs.oasis-open.org/odata/ns/metadata" xmlns:d="http://docs.oasis-open.org/odata/ns/data" xmlns:gml="http://www.opengis.net/gml" xmlns:georss="http://www.georss.org/georss"><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>
</m:properties>
</content>
</entry>
{code}
the following error is logged in the server:
{noformat}
09:54:38,069 WARN [org.teiid.ODATA] (http-/0.0.0.0:8080-1) TEIID16050 Unable to process odata request due to: An I/O exception occurred. with cause Unsupported encoding: IBM1252: Unsupported encoding: IBM1252
at org.apache.olingo.server.core.deserializer.xml.ODataXmlDeserializer.entity(ODataXmlDeserializer.java:592)
at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.getEntityFromClient(DataRequest.java:367)
at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.execute(DataRequest.java:359)
at org.apache.olingo.server.core.requests.DataRequest.execute(DataRequest.java:255)
at org.apache.olingo.server.core.ServiceDispatcher.internalExecute(ServiceDispatcher.java:160)
at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:98)
at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:66)
at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:43) [teiid-olingo-8.12.5.redhat-4.jar:8.12.5.redhat-4]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:226) [teiid-olingo-8.12.5.redhat-4.jar:8.12.5.redhat-4]
at org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) [teiid-olingo-8.12.5.redhat-4.jar:8.12.5.redhat-4]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.4.Final-redhat-4.jar:7.5.4.Final-redhat-4]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_79]
Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: IBM1252
at com.ctc.wstx.io.StreamBootstrapper.bootstrapInput(StreamBootstrapper.java:247)
at com.ctc.wstx.stax.WstxInputFactory.doCreateSR(WstxInputFactory.java:546)
at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:600)
at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:615)
at com.ctc.wstx.stax.WstxInputFactory.createXMLEventReader(WstxInputFactory.java:269)
at __redirected.__XMLInputFactory.createXMLEventReader(__XMLInputFactory.java:170) [jboss-modules.jar:1.3.7.Final-redhat-1]
at org.apache.olingo.server.core.deserializer.xml.ODataXmlDeserializer.getReader(ODataXmlDeserializer.java:97)
at org.apache.olingo.server.core.deserializer.xml.ODataXmlDeserializer.entity(ODataXmlDeserializer.java:583)
... 26 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months