December 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2766) OData large batch size does not allow all results to be returned to the client in a single batch

by Marc Shirley (JIRA)

Marc Shirley created TEIID-2766: ----------------------------------- Summary: OData large batch size does not allow all results to be returned to the client in a single batch Key: TEIID-2766 URL: https://issues.jboss.org/browse/TEIID-2766 Project: Teiid Issue Type: Bug Affects Versions: 8.4 Environment: OData client connecting to Teiid Reporter: Marc Shirley Assignee: Steven Hawkins OData large batch-size, for example -1 to get all results in 1 response, doesn't work. Largest tested value that does work 51210. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2729) Dynamic VDB xml requires sibling elements to be in a certain order

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2729?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2729: ---------------------------------- Fix Version/s: 8.7 We'll look at doing this in 8.7 > Dynamic VDB xml requires sibling elements to be in a certain order > ------------------------------------------------------------------ > > Key: TEIID-2729 > URL: https://issues.jboss.org/browse/TEIID-2729 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Affects Versions: 8.5 > Reporter: Mark Drilling > Assignee: Steven Hawkins > Fix For: 8.7 > > > In my *-vdb.xml, I have a model defined per following snippet: > <model name="myModel" type="PHYSICAL" visible="true"> > <source name="myModel" translator-name="hive" connection-jndi-name="Hive12Src" /> > <property name="trimColumnNames" value="true" /> > </model> > The vdb.xml failed to parse, so I moved the <property> element ahead of <source> and then it worked. > I don't think element ordering should matter in this case? -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2757) XML 1.0 invalid characters not supported in Odata Atom feed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2757: --------------------------------------- > How do I set the property with See https://docs.jboss.org/author/display/TEIID/OData+Support it is set for all odata requests. > Is it not safer to replace these also? There's a distinction to be made between invalid and the compatibility characters you are mentioning. The use of compatibility characters is discouraged, but not invalid. Thus there's no exception produced by Woodstox. As to whether it's better to replace them as well, that doesn't seem like something that we should assume. > And in which enterprise version is this change to be included? Again that is not a question that can be fully answered in the community. Please contact support. > XML 1.0 invalid characters not supported in Odata Atom feed > ----------------------------------------------------------- > > Key: TEIID-2757 > URL: https://issues.jboss.org/browse/TEIID-2757 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Environment: EAP version 6.1 with Teiid 8.5 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.7 > > Attachments: List of invalid XML characters.docx, TEIID-2757-Webservices-Stacktrace.txt > > > The odata framework sometimes has problems with transforming characters (invalid in XML 1.0) from the source data to the XML result. The result is an exception: TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x1b) in text to output (in xml 1.1, could output as a character entity). -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2757) XML 1.0 invalid characters not supported in Odata Atom feed

by Patrick Deenen (JIRA)

[ https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin... ] Patrick Deenen commented on TEIID-2757: --------------------------------------- Thanks for this solution. How do I set the property with [1] Plain HTTP client doing Odata request with a URL? [2] Web services? And some feedback on the change: In Row 379 LocalClient.java - only checks for characters <= 0x0020 But I understand that there are more invalid characters in XML 1.0: • \u007F - \u0084 • \u0086 - \u009F • \uD800 - \uDFFF • \uFDD0 - \uFDEF; \uFFFE; \uFFFF Is it not safer to replace these also? And in which enterprise version is this change to be included? > XML 1.0 invalid characters not supported in Odata Atom feed > ----------------------------------------------------------- > > Key: TEIID-2757 > URL: https://issues.jboss.org/browse/TEIID-2757 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Environment: EAP version 6.1 with Teiid 8.5 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.7 > > Attachments: List of invalid XML characters.docx, TEIID-2757-Webservices-Stacktrace.txt > > > The odata framework sometimes has problems with transforming characters (invalid in XML 1.0) from the source data to the XML result. The result is an exception: TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x1b) in text to output (in xml 1.1, could output as a character entity). -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2757) XML 1.0 invalid characters not supported in Odata Atom feed

by Patrick Deenen (JIRA)

[ https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin... ] Patrick Deenen updated TEIID-2757: ---------------------------------- Attachment: List of invalid XML characters.docx See attached document for the summary of invalid XML 1.0 characters. > XML 1.0 invalid characters not supported in Odata Atom feed > ----------------------------------------------------------- > > Key: TEIID-2757 > URL: https://issues.jboss.org/browse/TEIID-2757 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Environment: EAP version 6.1 with Teiid 8.5 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.7 > > Attachments: List of invalid XML characters.docx, TEIID-2757-Webservices-Stacktrace.txt > > > The odata framework sometimes has problems with transforming characters (invalid in XML 1.0) from the source data to the XML result. The result is an exception: TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x1b) in text to output (in xml 1.1, could output as a character entity). -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2458) Sybase15 subquery using HAVING clause failing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2458?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2458: ------------------------------------------------ belong(a)redhat.com changed the Status of [bug 996550|https://bugzilla.redhat.com/show_bug.cgi?id=996550] from MODIFIED to ON_QA > Sybase15 subquery using HAVING clause failing > --------------------------------------------- > > Key: TEIID-2458 > URL: https://issues.jboss.org/browse/TEIID-2458 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Example query is failing: SELECT INTKEY, STRINGKEY, FLOATNUM FROM BQT1.SMALLA GROUP BY INTKEY, STRINGKEY, FLOATNUM HAVING FLOATNUM = (SELECT FLOATNUM FROM BQT1.SMALLA WHERE STRINGKEY = 20) > When this query is submitted through EDS using Squirrel or BQT as a client it returns: > IntKey StringKey > 20 20 0 > When the resulting source-specific query generated from EDS is submitted direct to Sybase15 the same results are returned. > SELECT g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real) FROM SmallA g_0 WHERE cast(g_0.FloatNum AS real) = (SELECT cast(g_1.FloatNum AS real) FROM SmallA g_1 WHERE g_1.StringKey = '20') GROUP BY g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real)is submitted direct to Sybase15 > RESULTS > IntKey StringKey > 20 20 0 > However, when the GROUP BY is removed from the query it returns the expected results as shown below: > IntKey StringKey > 20 20 -4 > The supporting VDB can be provided if needed. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2757) XML 1.0 invalid characters not supported in Odata Atom feed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2757. ----------------------------------- Resolution: Done Added an odata configuration property - invalid-xml10-character-replacement - that can be set to the desired replacement string should an invalid character be encountered. Unfortunately this affects both xml and json results. The default behavior remains as throwing an exception. Users can also use the workarounds listed in this issue. > XML 1.0 invalid characters not supported in Odata Atom feed > ----------------------------------------------------------- > > Key: TEIID-2757 > URL: https://issues.jboss.org/browse/TEIID-2757 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Environment: EAP version 6.1 with Teiid 8.5 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.7 > > Attachments: TEIID-2757-Webservices-Stacktrace.txt > > > The odata framework sometimes has problems with transforming characters (invalid in XML 1.0) from the source data to the XML result. The result is an exception: TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x1b) in text to output (in xml 1.1, could output as a character entity). -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2765) Add odata support for array types

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2765: ------------------------------------- Summary: Add odata support for array types Key: TEIID-2765 URL: https://issues.jboss.org/browse/TEIID-2765 Project: Teiid Issue Type: Enhancement Components: Server Reporter: Steven Hawkins Assignee: Steven Hawkins simple type arrays should be supported through odata with a mapping to a complex type. It would be good to also support object type values also but that would seemingly be a large effort possibly involving custom odata4j serializers to define the complex type metadata and perform the serialization to a complex type value. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2757) XML 1.0 invalid characters not supported in Odata Atom feed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin... ] Work on TEIID-2757 started by Steven Hawkins. > XML 1.0 invalid characters not supported in Odata Atom feed > ----------------------------------------------------------- > > Key: TEIID-2757 > URL: https://issues.jboss.org/browse/TEIID-2757 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Environment: EAP version 6.1 with Teiid 8.5 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.7 > > Attachments: TEIID-2757-Webservices-Stacktrace.txt > > > The odata framework sometimes has problems with transforming characters (invalid in XML 1.0) from the source data to the XML result. The result is an exception: TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x1b) in text to output (in xml 1.1, could output as a character entity). -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2757) XML 1.0 invalid characters not supported in Odata Atom feed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2757: --------------------------------------- Since there is no standard xmloutputfactory option for invalid character replacement, odata4j does not presume the use of woodstox, and there's no simple path for user interaction of the xmloutputfactory to set a woodstox specific property it's fairly safe to assume that this will not be addressed as an enhancement by odata4j. > XML 1.0 invalid characters not supported in Odata Atom feed > ----------------------------------------------------------- > > Key: TEIID-2757 > URL: https://issues.jboss.org/browse/TEIID-2757 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Environment: EAP version 6.1 with Teiid 8.5 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.7 > > Attachments: TEIID-2757-Webservices-Stacktrace.txt > > > The odata framework sometimes has problems with transforming characters (invalid in XML 1.0) from the source data to the XML result. The result is an exception: TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x1b) in text to output (in xml 1.1, could output as a character entity). -- 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

11 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2013