[teiid-issues] [JBoss JIRA] (TEIID-4782) Change framework to catch RutineException from translator/connector

[Ramesh Reddy (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-4782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy resolved TEIID-4782.
---------------------------------
    Fix Version/s: 9.3
                   9.2.1
                   9.1.4
       Resolution: Done
           Labels: Alpaha1  (was: )


Wrapped the RuntimeException inside the TranslatorException before bubbling into any engine specific code. Any run away RuntimeExceptions should be caught here.

> Change framework to catch RutineException from translator/connector
> -------------------------------------------------------------------
>
>                 Key: TEIID-4782
>                 URL: https://issues.jboss.org/browse/TEIID-4782
>             Project: Teiid
>          Issue Type: Sub-task
>          Components: Query Engine
>    Affects Versions: 9.3
>            Reporter: Van Halbert
>            Assignee: Ramesh Reddy
>              Labels: Alpaha1
>             Fix For: 9.3, 9.2.1, 9.1.4
>
>
> Discussion:
> Generally the connector/engine logic should be responsible for handling whatever exception is thrown.  For example ConnectorWorkItem and DataTeirTupleSource do intercept RuntimeExceptions, but rethrows them.  We may want to instead convert them into Processing exceptions as the ConnectorWorkItem level.
> ----- Original Message -----
> > With Resource-adapters, the drivers to connect to some of these data sources
> > are not standard.  And because of that, just like with JDG, its probable
> > that other drivers will be throwing unexpected exceptions when those data
> > sources are scaled up and down.   I know the supporting of other RA data
> > sources is probably not real close, but would it be pro-active to look at
> > possible RA's and that may need to have try/catches added?
> >
> > Van
> > 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)