[JBoss JIRA] (TEIID-4782) Change framework to catch RutineException from translator/connector
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4782?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4782:
------------------------------------------------
jolee(a)redhat.com changed the Status of [bug 1428414|https://bugzilla.redhat.com/show_bug.cgi?id=1428414] from NEW to CLOSED
> 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, 8.12.10.6_3
>
>
> 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)
7 years, 10 months
[JBoss JIRA] (TEIID-4572) Grouping by and faceted search for Solr tranlator
by Amr Ismail (JIRA)
[ https://issues.jboss.org/browse/TEIID-4572?page=com.atlassian.jira.plugin... ]
Amr Ismail edited comment on TEIID-4572 at 3/6/17 10:34 AM:
------------------------------------------------------------
Handling group by clause in Teiid Solr translator module
Teiid Solr translator neglects grouping in Teiid query. We modified it to accept grouping and count(*) function in select clause. Furthermore, we support grouping by date field using PARSETIMESTAMP(FORMATTIMESTAMP('dateField', 'dateFormat'), 'dateFormat') Teiid function with these gap values: minute, hour, day, month and year according to dateFormat. For example, if dateFormat="yyyy-MM-dd" then gap=1DAY and if dateFormat="yyyy-MM-dd HH" then gap=1HOUR.
We used facet pivot to group by more than one facet field in Solr. This enabled us from grouping by multiple fields. After that we worked on date ranges in Solr, to be able to add date ranges inside the facet pivot query. After adding date ranges to the facet pivot, now we are able to group by any number of fields and with date ranges also.
We developed some test cases in calss "TestTeiidLanguageGroupingToSolr" to test grouping by single field, by multiple fields and by date ranges combined with other fields.
Please refer to the "TestTeiidLanguageGroupingToSolr" class to see more examples
was (Author: amr_alaa):
Handling group by clause in Teiid Solr translator module
Teiid Solr translator neglects grouping in Teiid query. We modified it to accept grouping and count(*) function in select clause. Furthermore, we support grouping by date field using PARSETIMESTAMP(FORMATTIMESTAMP('dateField', 'dateFormat'), 'dateFormat') Teiid function with these gap values: minute, hour, day, month and year according to dateFormat. For example, if dateFormat="yyyy-MM-dd" then gap=1DAY and if dateFormat="yyyy-MM-dd HH" then gap=1HOUR.
We developed some test cases in calss "TestTeiidLanguageGroupingToSolr" to test grouping by single field, by multiple fields and by date ranges combined with other fields.
Please refer to the "TestTeiidLanguageGroupingToSolr" class to see more examples
> Grouping by and faceted search for Solr tranlator
> -------------------------------------------------
>
> Key: TEIID-4572
> URL: https://issues.jboss.org/browse/TEIID-4572
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Hend Amin
> Fix For: Open To Community
>
>
> Currently group by is not supported for Solr translator. For example:
> select x,y, count\(*) from solr_core group by x,y; the corresponding Solr request does not contain group by.
> Please add group by and faceted search support for Solr translator.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4572) Grouping by and faceted search for Solr tranlator
by Amr Ismail (JIRA)
[ https://issues.jboss.org/browse/TEIID-4572?page=com.atlassian.jira.plugin... ]
Amr Ismail edited comment on TEIID-4572 at 3/6/17 10:28 AM:
------------------------------------------------------------
Handling group by clause in Teiid Solr translator module
Teiid Solr translator neglects grouping in Teiid query. We modified it to accept grouping and count(*) function in select clause. Furthermore, we support grouping by date field using PARSETIMESTAMP(FORMATTIMESTAMP('dateField', 'dateFormat'), 'dateFormat') Teiid function with these gap values: minute, hour, day, month and year according to dateFormat. For example, if dateFormat="yyyy-MM-dd" then gap=1DAY and if dateFormat="yyyy-MM-dd HH" then gap=1HOUR.
We developed some test cases in calss "TestTeiidLanguageGroupingToSolr" to test grouping by single field, by multiple fields and by date ranges combined with other fields.
Please refer to the "TestTeiidLanguageGroupingToSolr" class to see more examples
was (Author: amr_alaa):
Handling group by clause in Teiid Solr translator module
Teiid Solr translator neglects grouping in Teiid query. We modified it to accept grouping and count(*) function in select clause. Furthermore, we support grouping by date field using PARSETIMESTAMP(FORMATTIMESTAMP('dateField', 'dateFormat'), 'dateFormat') Teiid function with these gap values: minute, hour, day, month and year according to dateFormat. For example, if dateFormat="yyyy-MM-dd" then gap=1DAY and if dateFormat="yyyy-MM-dd HH" then gap=1HOUR.
We developed some test cases in calss "TestTeiidLanguageGroupingToSolr" to test grouping by single field, by multiple fields and by date ranges combined with other fields.
Please refer to the "TestTeiidLanguageGroupingToSolr" class to see more examples
> Grouping by and faceted search for Solr tranlator
> -------------------------------------------------
>
> Key: TEIID-4572
> URL: https://issues.jboss.org/browse/TEIID-4572
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Hend Amin
> Fix For: Open To Community
>
>
> Currently group by is not supported for Solr translator. For example:
> select x,y, count\(*) from solr_core group by x,y; the corresponding Solr request does not contain group by.
> Please add group by and faceted search support for Solr translator.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4572) Grouping by and faceted search for Solr tranlator
by Amr Ismail (JIRA)
[ https://issues.jboss.org/browse/TEIID-4572?page=com.atlassian.jira.plugin... ]
Amr Ismail edited comment on TEIID-4572 at 3/6/17 10:27 AM:
------------------------------------------------------------
Handling group by clause in Teiid Solr translator module
Teiid Solr translator neglects grouping in Teiid query. We modified it to accept grouping and count(*) function in select clause. Furthermore, we support grouping by date field using PARSETIMESTAMP(FORMATTIMESTAMP('dateField', 'dateFormat'), 'dateFormat') Teiid function with these gap values: minute, hour, day, month and year according to dateFormat. For example, if dateFormat="yyyy-MM-dd" then gap=1DAY and if dateFormat="yyyy-MM-dd HH" then gap=1HOUR.
We developed some test cases in calss "TestTeiidLanguageGroupingToSolr" to test grouping by single field, by multiple fields and by date ranges combined with other fields.
Please refer to the "TestTeiidLanguageGroupingToSolr" class to see more examples
was (Author: amr_alaa):
Handling group by clause in Teiid Solr translator module
Teiid Solr translator neglects grouping in Teiid query. We modified it to accept grouping and count(*) function in select clause. Furthermore, we support grouping by date field using PARSETIMESTAMP(FORMATTIMESTAMP('dateField', 'dateFormat'), 'dateFormat') Teiid function with these gap values: minute, hour, day, month and year according to dateFormat. For example, if dateFormat="yyyy-MM-dd" then gap=1DAY and if dateFormat="yyyy-MM-dd HH" then gap=1HOUR.
We developed some test cases in calss "TestTeiidLanguageGroupingToSolr" to test grouping by single field, by multiple fields and by date ranges combined with other fields.
Please refer to the "TestTeiidLanguageGroupingToSolr" class to see more examples
> Grouping by and faceted search for Solr tranlator
> -------------------------------------------------
>
> Key: TEIID-4572
> URL: https://issues.jboss.org/browse/TEIID-4572
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Hend Amin
> Fix For: Open To Community
>
>
> Currently group by is not supported for Solr translator. For example:
> select x,y, count\(*) from solr_core group by x,y; the corresponding Solr request does not contain group by.
> Please add group by and faceted search support for Solr translator.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4572) Grouping by and faceted search for Solr tranlator
by Amr Ismail (JIRA)
[ https://issues.jboss.org/browse/TEIID-4572?page=com.atlassian.jira.plugin... ]
Amr Ismail commented on TEIID-4572:
-----------------------------------
Handling group by clause in Teiid Solr translator module
Teiid Solr translator neglects grouping in Teiid query. We modified it to accept grouping and count(*) function in select clause. Furthermore, we support grouping by date field using PARSETIMESTAMP(FORMATTIMESTAMP('dateField', 'dateFormat'), 'dateFormat') Teiid function with these gap values: minute, hour, day, month and year according to dateFormat. For example, if dateFormat="yyyy-MM-dd" then gap=1DAY and if dateFormat="yyyy-MM-dd HH" then gap=1HOUR.
We developed some test cases in calss "TestTeiidLanguageGroupingToSolr" to test grouping by single field, by multiple fields and by date ranges combined with other fields.
Please refer to the "TestTeiidLanguageGroupingToSolr" class to see more examples
> Grouping by and faceted search for Solr tranlator
> -------------------------------------------------
>
> Key: TEIID-4572
> URL: https://issues.jboss.org/browse/TEIID-4572
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Hend Amin
> Fix For: Open To Community
>
>
> Currently group by is not supported for Solr translator. For example:
> select x,y, count\(*) from solr_core group by x,y; the corresponding Solr request does not contain group by.
> Please add group by and faceted search support for Solr translator.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4797) Oracle: empty catalog messed up VDB schemas name
by Ivan Chan (JIRA)
[ https://issues.jboss.org/browse/TEIID-4797?page=com.atlassian.jira.plugin... ]
Ivan Chan commented on TEIID-4797:
----------------------------------
More details here:
https://developer.jboss.org/message/969506?et=watches.email.thread#969506
> Oracle: empty catalog messed up VDB schemas name
> -------------------------------------------------
>
> Key: TEIID-4797
> URL: https://issues.jboss.org/browse/TEIID-4797
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 9.1.1
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
>
> I recently upgraded from Teiid 8.12.3 to version 9.1.1. And I found query transformation problem for oracle 12c.
>
> I have a simple query. See below:
>
> select "STORE_CITY"
> from "jasperserver_FOODMART"."STORE"
> limit 200001
>
> However, teiid version 9.1.1 transformed the query to
>
> Caused by: org.teiid.jdbc.TeiidSQLException: TEIID30504 1017993016: 1741 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT c_0 FROM (SELECT g_0."STORE_CITY" AS c_0 FROM "FOODMART".""."STORE" g_0) WHERE ROWNUM <= 200001]
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:723)
> at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:65)
> at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:561)
> at org.teiid.client.util.ResultsFuture.addCompletionListener(ResultsFuture.java:148)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:557)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:317)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:76)
> It looks like it's returning an empty string for the catalog. The code currently expects a non-null to indicate the package name.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4797) Oracle: empty catalog messed up VDB schemas name
by Ivan Chan (JIRA)
Ivan Chan created TEIID-4797:
--------------------------------
Summary: Oracle: empty catalog messed up VDB schemas name
Key: TEIID-4797
URL: https://issues.jboss.org/browse/TEIID-4797
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 9.1.1
Reporter: Ivan Chan
Assignee: Steven Hawkins
I recently upgraded from Teiid 8.12.3 to version 9.1.1. And I found query transformation problem for oracle 12c.
I have a simple query. See below:
select "STORE_CITY"
from "jasperserver_FOODMART"."STORE"
limit 200001
However, teiid version 9.1.1 transformed the query to
Caused by: org.teiid.jdbc.TeiidSQLException: TEIID30504 1017993016: 1741 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT c_0 FROM (SELECT g_0."STORE_CITY" AS c_0 FROM "FOODMART".""."STORE" g_0) WHERE ROWNUM <= 200001]
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:723)
at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:65)
at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:561)
at org.teiid.client.util.ResultsFuture.addCompletionListener(ResultsFuture.java:148)
at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:557)
at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:317)
at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:76)
It looks like it's returning an empty string for the catalog. The code currently expects a non-null to indicate the package name.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4782) Change framework to catch RutineException from translator/connector
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4782?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4782:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1428414, https://bugzilla.redhat.com/show_bug.cgi?id=1428416
Bugzilla Update: Perform
> 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, 8.12.10.6_3
>
>
> 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)
7 years, 10 months