October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3489) Can a function be added to filter certain ASCII chars below 31 and above 127 out of an XML Document

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3489?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3489: --------------------------------------- If the document is small and can be cast to a string, then the 8.12 regex replace function could be used: regexpReplace(doc, '[^\x09\x0A\x0D\x20-\x7E]', '', 'g') That will remove all invalid ascii characters. > Can a function be added to filter certain ASCII chars below 31 and above 127 out of an XML Document > --------------------------------------------------------------------------------------------------- > > Key: TEIID-3489 > URL: https://issues.jboss.org/browse/TEIID-3489 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Debbie Steigner > Priority: Minor > Fix For: 9.0 > > > Add a function in Teiid to filter off all ASCII chars below 31 and above 127. > web service data source that contains control characters due to data entered by copy and paste the text from another system. > The characters in this instance were the print control chars ASCII 28 and 29, File Separator and Group Separator respectively. These are used for formatting in older systems. Unfortunately, the XML standard prohibits the processing of all ASCII characters below 31 apart from Tab, Line Feed and Carriage Return which are permissible. Also, ASCII chars above 127 to 255 will also cause XML parsers to crash. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3754) Remove OData V2 implementation of the Server

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3754?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3754: ------------------------------------- Yes, I contributed that to Olingo with https://issues.apache.org/jira/browse/OLINGO-640 > Remove OData V2 implementation of the Server > -------------------------------------------- > > Key: TEIID-3754 > URL: https://issues.jboss.org/browse/TEIID-3754 > Project: Teiid > Issue Type: Task > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.0 > > > We need to remove server implementation of OData V2 specification from Teiid in favor of OData V4. > The OData V2 translator, we should keep, however that may needs to be updated/re-written using the Olingo. However that is separate issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3753) Change widenComparisonToString to false by default

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3753?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3753: --------------------------------------- Changed the default - but only so it affects dqp/server level tests. A lot of our engine tests will need corrected if we push this down more. > Change widenComparisonToString to false by default > -------------------------------------------------- > > Key: TEIID-3753 > URL: https://issues.jboss.org/browse/TEIID-3753 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > TEIID-3722 added an option to not widen comparisons to string, but defaulted to true to maintain legacy compatibility. It's more consistent with other databases to default to false. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3754) Remove OData V2 implementation of the Server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3754?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3754: --------------------------------------- Just to make sure, v4 now supports both atom and json? > Remove OData V2 implementation of the Server > -------------------------------------------- > > Key: TEIID-3754 > URL: https://issues.jboss.org/browse/TEIID-3754 > Project: Teiid > Issue Type: Task > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.0 > > > We need to remove server implementation of OData V2 specification from Teiid in favor of OData V4. > The OData V2 translator, we should keep, however that may needs to be updated/re-written using the Olingo. However that is separate issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3436) Add array type support to the odata translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3436?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3436: ------------------------------------- I will see if I can take a look at fixing that. > Add array type support to the odata translator > ---------------------------------------------- > > Key: TEIID-3436 > URL: https://issues.jboss.org/browse/TEIID-3436 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.12.x > > > Arrays of basic types in odata responses should be convertible into a runtime array type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3754) Remove OData V2 implementation of the Server

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3754: ----------------------------------- Summary: Remove OData V2 implementation of the Server Key: TEIID-3754 URL: https://issues.jboss.org/browse/TEIID-3754 Project: Teiid Issue Type: Task Components: OData Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 9.0 We need to remove server implementation of OData V2 specification from Teiid in favor of OData V4. The OData V2 translator, we should keep, however that may needs to be updated/re-written using the Olingo. However that is separate issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3436) Add array type support to the odata translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3436?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3436: --------------------------------------- > if that is not working it is a regression/bug No, it never worked from what I can tell. OData4j simply doesn't support reading collection types in atom feeds. > Add array type support to the odata translator > ---------------------------------------------- > > Key: TEIID-3436 > URL: https://issues.jboss.org/browse/TEIID-3436 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.12.x > > > Arrays of basic types in odata responses should be convertible into a runtime array type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3436) Add array type support to the odata translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3436?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3436: ------------------------------------- Is it sufficient if we support the read of the array types? I thought we already did that, if that is not working it is a regression/bug. > Add array type support to the odata translator > ---------------------------------------------- > > Key: TEIID-3436 > URL: https://issues.jboss.org/browse/TEIID-3436 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.12.x > > > Arrays of basic types in odata responses should be convertible into a runtime array type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3708) Undeployable dynamic VDB at start-up time removes all previously deployed artifacts

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3708?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3708: ------------------------------------- Needs a fix in EAP > Undeployable dynamic VDB at start-up time removes all previously deployed artifacts > ----------------------------------------------------------------------------------- > > Key: TEIID-3708 > URL: https://issues.jboss.org/browse/TEIID-3708 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 8.12 > > > If standalone/deployments directory contains undeployable dynamic VDB at start-up (reload) time all deployments previously deployed via mangement CLI are undeployed. > Log: > {code:text} > 13:42:48,993 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss Red Hat JBoss Data Virtualization 6.2.0 (AS 7.5.3.Final-redhat-2) starting > ... > ... > ... > 13:42:53,258 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "oo-vdb.xml")]) - failure description: {"JBAS014671: Failed services" => {"jboss.teiid.vdb.odata.1" => "org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1 > Caused by: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1"}} > 13:42:53,300 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015859: Deployed "QT_MySql55_Push.vdb" (runtime-name : "QT_MySql55_Push.vdb") > 13:42:53,301 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "oo-vdb.xml" (runtime-name : "oo-vdb.xml") > 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 52) JBAS015859: Deployed "modeshape-cmis.war" (runtime-name : "modeshape-cmis.war") > 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "integration-platform-console.war" (runtime-name : "integration-platform-console.war") > 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 52) JBAS015859: Deployed "modeshape-webdav.war" (runtime-name : "modeshape-webdav.war") > 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 52) JBAS015859: Deployed "modeshape-rest.war" (runtime-name : "modeshape-rest.war") > 13:42:53,303 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.teiid.vdb.odata.1: org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1 > 13:42:53,330 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management > 13:42:53,330 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 > 13:42:53,331 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss Red Hat JBoss Data Virtualization 6.2.0 (AS 7.5.3.Final-redhat-2) started (with errors) in 4336ms - Started 619 of 664 services (1 services failed or missing dependencies, 100 services are lazy, passive or on-demand) > 13:42:53,529 INFO [org.jboss.web] (ServerService Thread Pool -- 26) JBAS018224: Unregister web context: /modeshape-rest > 13:42:53,538 INFO [org.jboss.web] (ServerService Thread Pool -- 19) JBAS018224: Unregister web context: /modeshape-webdav > 13:42:53,540 INFO [org.jboss.web] (ServerService Thread Pool -- 18) JBAS018224: Unregister web context: /modeshape-cmis > 13:42:53,544 INFO [org.teiid.RUNTIME] (MSC service thread 1-4) TEIID50026 VDB "QT_MySql55_Push.1[Source{Source=Source, mysql5, MySQL55_PushDS}, XQTRecursiveSchema{}, BQT2{}, SP{SP=SP, mysql5, MySQL55_PushDS}, VirtProcs{}, XQTSchema{}, XQTRecursiveDoc{}, XQT{}, BQT1{}, VQT{}, XQTNestedDoc{}, XQTDoc{}]" undeployed. > 13:42:53,569 INFO [javax.enterprise.resource.webservices.jaxws.servlet.http] (ServerService Thread Pool -- 18) WSSERVLET15: JAX-WS servlet destroyed > 13:42:53,572 INFO [javax.enterprise.resource.webservices.jaxws.server.http] (ServerService Thread Pool -- 18) WSSERVLET13: JAX-WS context listener destroyed > 13:42:53,578 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment modeshape-rest.war (runtime-name: modeshape-rest.war) in 50ms > 13:42:53,580 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment oo-vdb.xml (runtime-name: oo-vdb.xml) in 43ms > 13:42:53,582 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment modeshape-webdav.war (runtime-name: modeshape-webdav.war) in 45ms > 13:42:53,583 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment QT_MySql55_Push.vdb (runtime-name: QT_MySql55_Push.vdb) in 46ms > 13:42:53,607 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment modeshape-cmis.war (runtime-name: modeshape-cmis.war) in 70ms > 13:42:53,647 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "oo-vdb.xml" (runtime-name: "oo-vdb.xml") > 13:42:53,648 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/45/9c1839c446e700d7f0b713f5f949b068fbeb24/content > 13:42:53,648 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "QT_MySql55_Push.vdb" (runtime-name: "QT_MySql55_Push.vdb") > 13:42:53,649 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/a3/b37a584c66a65d33bf194ffa9fc0e93c83b9ca/content > 13:42:53,649 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "modeshape-webdav.war" (runtime-name: "modeshape-webdav.war") > 13:42:53,651 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/f2/00c83231bcb7a63276d49ac9e01bcbbde30424/content > 13:42:53,651 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "modeshape-cmis.war" (runtime-name: "modeshape-cmis.war") > 13:42:53,652 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/2b/4d8dbcf74227d075e54215d1f330da494a4b22/content > 13:42:53,657 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "modeshape-rest.war" (runtime-name: "modeshape-rest.war") > 13:42:53,658 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.teiid.vdb.odata.1 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3685) org.teiid.padSpace does not affect to the "IN" operator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3685?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3685. --------------------------------- > org.teiid.padSpace does not affect to the "IN" operator > ------------------------------------------------------- > > Key: TEIID-3685 > URL: https://issues.jboss.org/browse/TEIID-3685 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1 > Environment: JBoss DV 6.1.2 > Reporter: hisao furuichi > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.4 > > Attachments: datasert.csv, INTERNAL_TEST.zip > > > org.teiid.padSpace does affect to "=" operator. But does not affect to "IN" operator. > [data for a column named "id"] > {noformat} > "test1 " > {noformat} > ["=" operator] I can get a result > {noformat} > SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id ='TEST1'; > {noformat} > ["IN" operator] I can not get a result > {noformat} > SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id IN ('TEST1', 'TEST2'); > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2015