[JBoss JIRA] (TEIID-2666) Extend OData output formats, currently JSON and XML supported
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2666?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-2666 at 5/15/14 1:58 PM:
----------------------------------------------------------------
Just wanted to add a comment; while I don't need CSV and can certainly use an ESB layer to handle streaming JSON transformations, it would be really useful to extend or change the JSON formatter without having to patch OData4j. Here's an example of what we do:
* The JSON initially looks either like so:
{code}
{
"d" : {
"results" : [
{
"__metadata" : {
"uri" : "http://somelongURL/odata/etc",
"type" : "SchemaName.TableName"
},
"COLUMN_A":value1,
"COLUMN_B":value1
},
{
"__metadata" : {
"uri" : "http://somelongURL/odata/etc",
"type" : "SchemaName.TableName"
},
"COLUMN_A":value2,
"COLUMN_B":value2
}
]
}
}
{code}
* Or like so:
{code}
{
"d" : {
{
"__metadata" : {
"uri" : "http://somelongURL/odata/etc",
"type" : "SchemaName.TableName"
},
"COLUMN_A":value1,
"COLUMN_B":value1
}
}
}
{code}
* And we want either this (1st case):
{code}
{
"TableNames" : [
{
"COLUMN_A":value1,
"COLUMN_B":value1
},
{
"COLUMN_A":value2,
"COLUMN_B":value2
}
]
}
{code}
* Or this (2nd case):
{code}
{
"TableName" : {
"COLUMN_A":value1,
"COLUMN_B":value1
}
}
{code}
It's really computationally intensive and expensive to have to reformat the JSON responses coming out of Teiid.
Thanks,
John Muller
was (Author: blue666man):
Just wanted to add a comment; while I don't need CSV and can certainly use an ESB layer to handle streaming JSON transformations, it would be really useful to extend or change the JSON formatter without having to patch OData4j. Here's an example of what we do:
# The JSON initially looks either like so:
{
"d" : {
"results" : [
{
"__metadata" : {
"uri" : "http://somelongURL/odata/etc",
"type" : "SchemaName.TableName"
},
"COLUMN_A":value1,
"COLUMN_B":value1
},
{
"__metadata" : {
"uri" : "http://somelongURL/odata/etc",
"type" : "SchemaName.TableName"
},
"COLUMN_A":value2,
"COLUMN_B":value2
}
]
}
}
# Or like so:
{
"d" : {
{
"__metadata" : {
"uri" : "http://somelongURL/odata/etc",
"type" : "SchemaName.TableName"
},
"COLUMN_A":value1,
"COLUMN_B":value1
}
}
}
# And we want either this (1st case):
{
"TableNames" : [
{
"COLUMN_A":value1,
"COLUMN_B":value1
},
{
"COLUMN_A":value2,
"COLUMN_B":value2
}
]
}
# Or this (2nd case):
{
"TableName" : {
"COLUMN_A":value1,
"COLUMN_B":value1
}
}
It's really computationally intensive and expensive to have to reformat the JSON responses coming out of Teiid.
Thanks,
John Muller
> Extend OData output formats, currently JSON and XML supported
> -------------------------------------------------------------
>
> Key: TEIID-2666
> URL: https://issues.jboss.org/browse/TEIID-2666
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.4
> Environment: N/A
> Reporter: Cojan van Ballegooijen
> Priority: Trivial
>
> We would like to see the available output formats of the OData services be extended with CSV (Command Seperated Values) upon customer request.
> It would be great if we could extend it ourselves using for example XSLT or other transformation mechanism.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2666) Extend OData output formats, currently JSON and XML supported
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2666?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2666:
---------------------------------------
> It's really computationally intensive and expensive to have to reformat the JSON responses coming out of Teiid.
It's not clear to me from the above what exactly you are looking for. Can you provide more context as to what the result represents and how/why you get the alternate form? Generally this breaks down along the lines of:
1. Is there an OData4j formatting bug?
2. Are you suggesting that is a compatible with the spec?
3. Is this something that is simply custom?
> Extend OData output formats, currently JSON and XML supported
> -------------------------------------------------------------
>
> Key: TEIID-2666
> URL: https://issues.jboss.org/browse/TEIID-2666
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.4
> Environment: N/A
> Reporter: Cojan van Ballegooijen
> Priority: Trivial
>
> We would like to see the available output formats of the OData services be extended with CSV (Command Seperated Values) upon customer request.
> It would be great if we could extend it ourselves using for example XSLT or other transformation mechanism.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2666) Extend OData output formats, currently JSON and XML supported
by John Muller (JIRA)
[ https://issues.jboss.org/browse/TEIID-2666?page=com.atlassian.jira.plugin... ]
John Muller commented on TEIID-2666:
------------------------------------
Just wanted to add a comment; while I don't need CSV and can certainly use an ESB layer to handle streaming JSON transformations, it would be really useful to extend or change the JSON formatter without having to patch OData4j. Here's an example of what we do:
# The JSON initially looks either like so:
{
"d" : {
"results" : [
{
"__metadata" : {
"uri" : "http://somelongURL/odata/etc",
"type" : "SchemaName.TableName"
},
"COLUMN_A":value1,
"COLUMN_B":value1
},
{
"__metadata" : {
"uri" : "http://somelongURL/odata/etc",
"type" : "SchemaName.TableName"
},
"COLUMN_A":value2,
"COLUMN_B":value2
}
]
}
}
# Or like so:
{
"d" : {
{
"__metadata" : {
"uri" : "http://somelongURL/odata/etc",
"type" : "SchemaName.TableName"
},
"COLUMN_A":value1,
"COLUMN_B":value1
}
}
}
# And we want either this (1st case):
{
"TableNames" : [
{
"COLUMN_A":value1,
"COLUMN_B":value1
},
{
"COLUMN_A":value2,
"COLUMN_B":value2
}
]
}
# Or this (2nd case):
{
"TableName" : {
"COLUMN_A":value1,
"COLUMN_B":value1
}
}
It's really computationally intensive and expensive to have to reformat the JSON responses coming out of Teiid.
Thanks,
John Muller
> Extend OData output formats, currently JSON and XML supported
> -------------------------------------------------------------
>
> Key: TEIID-2666
> URL: https://issues.jboss.org/browse/TEIID-2666
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.4
> Environment: N/A
> Reporter: Cojan van Ballegooijen
> Priority: Trivial
>
> We would like to see the available output formats of the OData services be extended with CSV (Command Seperated Values) upon customer request.
> It would be great if we could extend it ourselves using for example XSLT or other transformation mechanism.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2962) odata substring not working
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2962?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2962.
-----------------------------------
Fix Version/s: 8.8
Resolution: Done
Added substringof support using the locate function.
> odata substring not working
> ---------------------------
>
> Key: TEIID-2962
> URL: https://issues.jboss.org/browse/TEIID-2962
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.7
> Environment: CentOS
> Reporter: luca gioppo
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> When I try to execute a filter using the substring or the substringof functions I get an internal server error.
> 10:34:43,860 ERROR [org.teiid.ODATA] (ajp-/0.0.0.0:8009-5) null TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: Bad filter
> at org.odata4j.producer.resources.OptionsQueryParser.parseFilter(OptionsQueryParser.java:42) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntitiesImpl(EntitiesRequestResource.java:330) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntities(EntitiesRequestResource.java:266) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
> at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source) [:1.6.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_25]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_25]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:118) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.event(JBossWebContext.java:67)
> at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.invoke(JBossWebContext.java:48)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:488) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:420) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2962) odata substring not working
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2962?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2962:
-------------------------------------
I believe these did not have direct query substitutions in Teiid, thus got avoided at the time of development. We would need to add system functions then add support in Teiid then.
> odata substring not working
> ---------------------------
>
> Key: TEIID-2962
> URL: https://issues.jboss.org/browse/TEIID-2962
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.7
> Environment: CentOS
> Reporter: luca gioppo
> Assignee: Steven Hawkins
>
> When I try to execute a filter using the substring or the substringof functions I get an internal server error.
> 10:34:43,860 ERROR [org.teiid.ODATA] (ajp-/0.0.0.0:8009-5) null TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: Bad filter
> at org.odata4j.producer.resources.OptionsQueryParser.parseFilter(OptionsQueryParser.java:42) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntitiesImpl(EntitiesRequestResource.java:330) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntities(EntitiesRequestResource.java:266) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
> at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source) [:1.6.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_25]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_25]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:118) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.event(JBossWebContext.java:67)
> at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.invoke(JBossWebContext.java:48)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:488) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:420) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2962) odata substring not working
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2962?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2962:
---------------------------------------
I think this would fall under an enhancement as not all of the odata language has been implement. Not yet handled:
substringof
isof
date time offset literal
> odata substring not working
> ---------------------------
>
> Key: TEIID-2962
> URL: https://issues.jboss.org/browse/TEIID-2962
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.7
> Environment: CentOS
> Reporter: luca gioppo
> Assignee: Steven Hawkins
>
> When I try to execute a filter using the substring or the substringof functions I get an internal server error.
> 10:34:43,860 ERROR [org.teiid.ODATA] (ajp-/0.0.0.0:8009-5) null TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: Bad filter
> at org.odata4j.producer.resources.OptionsQueryParser.parseFilter(OptionsQueryParser.java:42) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntitiesImpl(EntitiesRequestResource.java:330) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntities(EntitiesRequestResource.java:266) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
> at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source) [:1.6.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_25]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_25]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:118) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.event(JBossWebContext.java:67)
> at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.invoke(JBossWebContext.java:48)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:488) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:420) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2962) odata substring not working
by luca gioppo (JIRA)
[ https://issues.jboss.org/browse/TEIID-2962?page=com.atlassian.jira.plugin... ]
luca gioppo commented on TEIID-2962:
------------------------------------
If you use a startswith it works.
Just the substring is crashing
> odata substring not working
> ---------------------------
>
> Key: TEIID-2962
> URL: https://issues.jboss.org/browse/TEIID-2962
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.7
> Environment: CentOS
> Reporter: luca gioppo
> Assignee: Steven Hawkins
>
> When I try to execute a filter using the substring or the substringof functions I get an internal server error.
> 10:34:43,860 ERROR [org.teiid.ODATA] (ajp-/0.0.0.0:8009-5) null TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: Bad filter
> at org.odata4j.producer.resources.OptionsQueryParser.parseFilter(OptionsQueryParser.java:42) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntitiesImpl(EntitiesRequestResource.java:330) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntities(EntitiesRequestResource.java:266) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
> at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source) [:1.6.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_25]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_25]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final.jar:]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:118) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.event(JBossWebContext.java:67)
> at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.invoke(JBossWebContext.java:48)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:488) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:420) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2962) odata substring not working
by luca gioppo (JIRA)
luca gioppo created TEIID-2962:
----------------------------------
Summary: odata substring not working
Key: TEIID-2962
URL: https://issues.jboss.org/browse/TEIID-2962
Project: Teiid
Issue Type: Bug
Components: OData
Affects Versions: 8.7
Environment: CentOS
Reporter: luca gioppo
Assignee: Steven Hawkins
When I try to execute a filter using the substring or the substringof functions I get an internal server error.
10:34:43,860 ERROR [org.teiid.ODATA] (ajp-/0.0.0.0:8009-5) null TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: Bad filter
at org.odata4j.producer.resources.OptionsQueryParser.parseFilter(OptionsQueryParser.java:42) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
at org.odata4j.producer.resources.EntitiesRequestResource.getEntitiesImpl(EntitiesRequestResource.java:330) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
at org.odata4j.producer.resources.EntitiesRequestResource.getEntities(EntitiesRequestResource.java:266) [odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar:]
at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source) [:1.6.0_25]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_25]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_25]
at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final.jar:]
at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final.jar:]
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final.jar:]
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final.jar:]
at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:118) [classes:]
at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.event(JBossWebContext.java:67)
at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.invoke(JBossWebContext.java:48)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:488) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:420) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2961) TEIID60016 Duplicate Column with h2 database
by Kenichi Takemura (JIRA)
[ https://issues.jboss.org/browse/TEIID-2961?page=com.atlassian.jira.plugin... ]
Kenichi Takemura closed TEIID-2961.
-----------------------------------
Resolution: Done
> TEIID60016 Duplicate Column with h2 database
> --------------------------------------------
>
> Key: TEIID-2961
> URL: https://issues.jboss.org/browse/TEIID-2961
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Reporter: Kenichi Takemura
> Assignee: Steven Hawkins
>
> I am trying to deploy a vdb.xml that has a physical datasouce with h2 translator. Teiid fails to deploy it with error 'TEIID60016 Duplicate Column'.
> Source database has a table that is 'sessions'. It seems getMetadata() from h2 database returns more columns for sessions table(user database + metadata for h2 itself?).
> It getting Duplicated 'ID' columns.
> On production we use mysql but on our test we want to use h2.
> Is this a bug in Teiid?
> Is there any workaround?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2961) TEIID60016 Duplicate Column with h2 database
by Kenichi Takemura (JIRA)
[ https://issues.jboss.org/browse/TEIID-2961?page=com.atlassian.jira.plugin... ]
Kenichi Takemura commented on TEIID-2961:
-----------------------------------------
importer.schemaPattern=PUBLIC worked. Closing..
> TEIID60016 Duplicate Column with h2 database
> --------------------------------------------
>
> Key: TEIID-2961
> URL: https://issues.jboss.org/browse/TEIID-2961
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Reporter: Kenichi Takemura
> Assignee: Steven Hawkins
>
> I am trying to deploy a vdb.xml that has a physical datasouce with h2 translator. Teiid fails to deploy it with error 'TEIID60016 Duplicate Column'.
> Source database has a table that is 'sessions'. It seems getMetadata() from h2 database returns more columns for sessions table(user database + metadata for h2 itself?).
> It getting Duplicated 'ID' columns.
> On production we use mysql but on our test we want to use h2.
> Is this a bug in Teiid?
> Is there any workaround?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month