May 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4220) Unsupported encoding when POSTing to odata on Windows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4220?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4220: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1339503 Bugzilla Update: Perform > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-3357) Add the final processor plan to the command log

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3357?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3357: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1325980|https://bugzilla.redhat.com/show_bug.cgi?id=1325980] from ON_QA to VERIFIED > Add the final processor plan to the command log > ----------------------------------------------- > > Key: TEIID-3357 > URL: https://issues.jboss.org/browse/TEIID-3357 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.11 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11, 8.7.6.6_2 > > > We should add the plan output not just once planning has completed, but when processing has completed as well so that the node statistics have been populated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-784) Enhance distinct set op processing

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-784?page=com.atlassian.jira.plugin.... ] Steven Hawkins resolved TEIID-784. ---------------------------------- Fix Version/s: (was: 9.0) Resolution: Deferred This is no longer needed for just distinct processing as that is performed with a tree. There is still the case of having an ordered distinct set op that could be enhanced in this way, but I'll mark that as deferred. > Enhance distinct set op processing > ---------------------------------- > > Key: TEIID-784 > URL: https://issues.jboss.org/browse/TEIID-784 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Priority: Minor > > The sort operation should be able to pushed for each set op child (distinct is already eligible for pushing, but typically won't be because there's no order by). Also for union the sorted children should be fed directly into the second phase of sorting. > All of this relies on the connector guaranteeing null ordering (TEIID-715 should be repurposed to cover the language enhancement of nulls first|last) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4208) Increase plan parallelism

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4208?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4208: ------------------------------------- interesting.. > Increase plan parallelism > ------------------------- > > Key: TEIID-4208 > URL: https://issues.jboss.org/browse/TEIID-4208 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > Increased parallelism within the plan, which includes parallelization of source queries via partitioning beyond multi-source and parallelizing the execution of union branches. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4219) Support variable and Parameters in HANA Translator

by Ted Jones (JIRA)

Ted Jones created TEIID-4219: -------------------------------- Summary: Support variable and Parameters in HANA Translator Key: TEIID-4219 URL: https://issues.jboss.org/browse/TEIID-4219 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 8.13.4 Reporter: Ted Jones Assignee: Ted Jones •Variables: A Variable can be specified before executing a query on the view. Usually variable values are entered manually by the user on a UI (variable popup). A variable defines a filter on an attribute of the view. Therefore it always has to be assigned to an attribute. The variable values are passed to the engine via the WHERE clause of the SQL statement. Variables are not known by the engine, but only by the clients like Datapreview, MDX, Advanced Analysis for Office or BO Explorer. It is the task of the client to convert the user input into the WHERE clause when accessing the data. •Parameters or Input Parameters: A parameter (like a variable) can be specified before executing a query on the view. Usually parameter values are entered manually by the user on a UI (variable popup). A Parameter defines an internal parameterization of the view. This means the engine needs to know it and uses the parameter value during the execution (e.g. to calculate a formula for a calculated measure). The parameter value is passed to the engine via the PLACEHOLDER clause of the SQL statement. A parameter can only have single values. For the end user there is no distinction between variables and parameters. Both appear as input fields on the variable popup. ------------------ There are 4 system tables under the schema _SYS_BI which contains information about Variables. · BIMC_VARIABLE · BIMC_VARIABLE_ASSIGNMENT · BIMC_VARIABLE_VIEW · BIMC_VARIABLE_VALUE SAP HANA documentation on Input parameters: http://help.sap.com/saphelp_hanaplatform/helpdata/en/d5/c8230abb571014acc... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4209) Primary key import fails with OSIsoft PI translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4209?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4209. ----------------------------------- Fix Version/s: 8.12.5 Resolution: Done Added a method to try both getShort and getInt when a short is expected. > Primary key import fails with OSIsoft PI translator > --------------------------------------------------- > > Key: TEIID-4209 > URL: https://issues.jboss.org/browse/TEIID-4209 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > As reported with https://developer.jboss.org/thread/269357 the PI driver does not support getShort for database metadata calls, even if that is expected by the JDBC spec. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4207) Limit pushdown is incorrect for simpledb

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4207?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4207: ---------------------------------- Summary: Limit pushdown is incorrect for simpledb (was: Limit pushdown is incorrect for simpldb) Are you having any success understanding what's needed for this issue? We'll want to get something in this week for a commit to 8.12.5. > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-4208) Increase plan parallelism

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4208?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4208: ---------------------------------- Component/s: Query Engine Fix Version/s: 9.1 (was: 9.x) Bucketing to 9.1 for further investigation. At least locally there's nothing promising about paralleling around just the sorting operations. I may need to test things out on machines with more cores with more realistic load scenarios. > Increase plan parallelism > ------------------------- > > Key: TEIID-4208 > URL: https://issues.jboss.org/browse/TEIID-4208 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > Increased parallelism within the plan, which includes parallelization of source queries via partitioning beyond multi-source and parallelizing the execution of union branches. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4180) Improve the documentation on ODBC SSL

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4180?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4180: --------------------------------------- Steve, yes this is documented, and in later versions 8.13+ ODBCRequireSecure is true by default with the configuration defaulted to disabled. > the server will allow non-SSL enabled ODBC traffic to connect to your SSL-secured port Which is also at the discretion of the client as it can be specify that ssl is required. > Improve the documentation on ODBC SSL > ------------------------------------- > > Key: TEIID-4180 > URL: https://issues.jboss.org/browse/TEIID-4180 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.0 > > > Update ODBC documentation with SSL. Related notes in > https://developer.jboss.org/wiki/JDBCODBCSSLConnectionUsingSelf-signedSSL... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4180) Improve the documentation on ODBC SSL

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIID-4180?page=com.atlassian.jira.plugin... ] Steve Tran commented on TEIID-4180: ----------------------------------- Might want to add this to the documentation as well. https://access.redhat.com/solutions/2180191 Basically with JDV 6.2.4, you need to pass in the -Dorg.teiid.ODBCRequireSecureSecure=true argument or else the server will allow non-SSL enabled ODBC traffic to connect to your SSL-secured port. After setting that flag, you'll need to specify <ssl mode="disabled" /> on any ODBC transport that you don't want to use SSL with. > Improve the documentation on ODBC SSL > ------------------------------------- > > Key: TEIID-4180 > URL: https://issues.jboss.org/browse/TEIID-4180 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.0 > > > Update ODBC documentation with SSL. Related notes in > https://developer.jboss.org/wiki/JDBCODBCSSLConnectionUsingSelf-signedSSL... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2016