[JBoss JIRA] (TEIID-2411) Add schema name to metadata validation messages
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2411?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2411.
---------------------------------
> Add schema name to metadata validation messages
> -----------------------------------------------
>
> Key: TEIID-2411
> URL: https://issues.jboss.org/browse/TEIID-2411
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.2
> Reporter: Paul Lysak
> Assignee: Ramesh Reddy
> Labels: CR1
> Fix For: 8.3
>
>
> Currently metadata validation messages don't contain schema name, so when working with lot of schemas it may be difficult to find out problematic element. For example, if table SOME_TABLE has no columns then
> org.teiid.query.metadata.MetadataValidator.MinimalMetadata.execute() will log following error message:
> TEIID31071 Invalid table; Table SOME_TABLE has no columns defined
> And there's no ability to detect later to which schema problematic table belongs.
> I suggest to append schema name - either by simple concatenation in MetadataValidator.java:
> metadataValidator.log(report, model, QueryPlugin.Util.gs(QueryPlugin.Event.TEIID31071, scmena.getName()+"."+t.getName()));
> or by changing message bundle i18n.properties:
> TEIID31071=Invalid table; Table {0}.{1} has no columns defined
> and providing message parameters in MetadataValidator.java:
> metadataValidator.log(report, model, QueryPlugin.Util.gs(QueryPlugin.Event.TEIID31071, scmena.getName(), t.getName()));
> There are also another validation messages in MetadataValidator.java which could be improved in similar way.
--
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, 9 months
[JBoss JIRA] (TEIID-2363) proactive buffering not occurring for the inner side of an outer join on "MERGE JOIN (SORT/ALREADY_SORTED)"
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2363?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2363.
---------------------------------
> proactive buffering not occurring for the inner side of an outer join on "MERGE JOIN (SORT/ALREADY_SORTED)"
> -----------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2363
> URL: https://issues.jboss.org/browse/TEIID-2363
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 7.7.2
> Reporter: Johnathon Lee
> Assignee: Steven Hawkins
> Fix For: 8.3, 7.7.6
>
>
> The issue here is this is an outer join and the inner side (the already sorted side) will be buffered regardless. Current logic does not catch blocked exceptions from one side and pro-actively buffer the other - rather we are serially performing the sort and then continue with the loading of the inner side
> For inner joins there is a clear trade-off between execution speed and buffering so this behavior may have to be hint or config driven for non-dependent non-outer joins.
--
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, 9 months
[JBoss JIRA] (TEIID-2412) OData does not handle exceptions correctly
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2412?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2412.
---------------------------------
> OData does not handle exceptions correctly
> ------------------------------------------
>
> Key: TEIID-2412
> URL: https://issues.jboss.org/browse/TEIID-2412
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: CR1
> Fix For: 8.3
>
>
> When a unexpected exception occurs, OData implementation masks correct error occurred and throws following
> {code}
> org.jboss.resteasy.core.ContextParameterInjector$GenericDelegatingProxy.invoke(ContextParameterInjector.java:53)
> $Proxy33.getBaseUri(Unknown Source)
> org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:54) org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:37) org.odata4j.producer.resources.ExceptionMappingProvider.getODataProducer(ExceptionMappingProvider.java:85) org.odata4j.producer.resources.ExceptionMappingProvider.toResponse(ExceptionMappingProvider.java:53)
> org.odata4j.producer.resources.ExceptionMappingProvider.toResponse(ExceptionMappingProvider.java:35) org.jboss.resteasy.core.SynchronousDispatcher.executeExceptionMapper(SynchronousDispatcher.java:324)
> org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:229) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:123)
> org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97)
> org.teiid.odata.ODataServlet.service(ODataServlet.java:61) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> {code}
--
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, 9 months