February 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3989) PartialResultsWarning not being returned

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3989?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3989: --------------------------------------- Ramesh that is not the case. The documentation unfortunately is not as complete as it should be. The other caveats are that the partial results warning need not be the head of the warning chain, and more importantly it may not be delivered with the initial results. In this case the first union branch is delivering a batch that will likely be feed all the way to the client before the exception from the second branch has been added for delivery. Only by actually cursoring through the results and re-checking the warnings (it helps to call clearWarnings after checking them) will the PartialResultsWarning be guaranteed to be seen. So I'll update the docs with this full accounting. > PartialResultsWarning not being returned > ---------------------------------------- > > Key: TEIID-3989 > URL: https://issues.jboss.org/browse/TEIID-3989 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.11.3, 9.0 > Reporter: Tom Arnold > Assignee: Steven Hawkins > Attachments: TeiidTest.zip, Test-vdb.xml, translator-test.zip > > > I'm trying to follow the example [here|https://docs.jboss.org/author/display/TEIID/Partial+Results+Mode] to return source failure information to my app. Partial results mode does work, but when used with a JBoss AS datasource (as opposed to standalone) {{TeiidSQLWarning}} is returned instead of the expected {{PartialResultsWarning}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3989) PartialResultsWarning not being returned

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3989?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3989: ------------------------------------- I think documentation needs to be updated, all warnings are reported as TeiidSQLWarning > PartialResultsWarning not being returned > ---------------------------------------- > > Key: TEIID-3989 > URL: https://issues.jboss.org/browse/TEIID-3989 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.11.3, 9.0 > Reporter: Tom Arnold > Assignee: Steven Hawkins > Attachments: TeiidTest.zip, Test-vdb.xml, translator-test.zip > > > I'm trying to follow the example [here|https://docs.jboss.org/author/display/TEIID/Partial+Results+Mode] to return source failure information to my app. Partial results mode does work, but when used with a JBoss AS datasource (as opposed to standalone) {{TeiidSQLWarning}} is returned instead of the expected {{PartialResultsWarning}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3898) Add OrientDB translator

by Tom Arnold (JIRA)

[ https://issues.jboss.org/browse/TEIID-3898?page=com.atlassian.jira.plugin... ] Tom Arnold commented on TEIID-3898: ----------------------------------- SQL reference [here|http://orientdb.com/docs/2.1/SQL.html]. Looks like next version (2.2) will have [OGC spatial support|http://orientdb.com/docs/2.1/Spatial-Index.html] (like PostGIS). Seems kind of like JPQL. Metadata processor could map "classes" as tables, and "links" as foreign keys. Noticed this neat trick in the JPA translator to only push down joins on foreign keys. {code} setSupportedJoinCriteria(SupportedJoinCriteria.KEY); {code} Not sure yet how to map some of the graph concepts. Maybe as predicate functions in the where clause? > Add OrientDB translator > ----------------------- > > Key: TEIID-3898 > URL: https://issues.jboss.org/browse/TEIID-3898 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Don Krapohl > Fix For: Open To Community > > > My organization has high-performance analytics on OrientDB graph databases. We use Teiid for centralized governance, access, etc. It would be beneficial to us if Teiid could translate to the SQL-like OrientDb syntax. Because there are many SQL-like syntax components of OrientDB's REST endpoints this should be fairly straightforward. > The OrientDB site is http://orientdb.com/. It's Apache 2 licensed, has a stable and mature community, has multiple releases, and provides multiple access methods (jdbc, odbc, REST). Work on the translator should not be wasted effort. > I can assist with testing if it would be helpful and if the translator is started I can assist in dev. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3989) PartialResultsWarning not being returned

by Tom Arnold (JIRA)

Tom Arnold created TEIID-3989: --------------------------------- Summary: PartialResultsWarning not being returned Key: TEIID-3989 URL: https://issues.jboss.org/browse/TEIID-3989 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 8.11.3, 9.0 Reporter: Tom Arnold Assignee: Steven Hawkins Attachments: TeiidTest.zip, Test-vdb.xml, translator-test.zip I'm trying to follow the example [here|https://docs.jboss.org/author/display/TEIID/Partial+Results+Mode] to return source failure information to my app. Partial results mode does work, but when used with a JBoss AS datasource (as opposed to standalone) {{TeiidSQLWarning}} is returned instead of the expected {{PartialResultsWarning}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3948) Provide a different mechanism to update odata wars

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3948?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3948: --------------------------------------- I've made the war names consistent with master and 8.12.x and added the start of odata4 documentation - https://github.com/teiid/teiid-documents/tree/master/client-dev Since it was copied from the v2 doc, it will still need further refinement and we'll probably need to expand on the deployment-overlay command. > Provide a different mechanism to update odata wars > -------------------------------------------------- > > Key: TEIID-3948 > URL: https://issues.jboss.org/browse/TEIID-3948 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > Directly modifying the wars under the base modules is a bad practice. We need to have users modify non-kit artifact files in a different location. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3988) Narrow when serial source access is used

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3988: ------------------------------------- Summary: Narrow when serial source access is used Key: TEIID-3988 URL: https://issues.jboss.org/browse/TEIID-3988 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0 Both when we determine a transaction is needed and how the processing is performed under a transaction can be improved. We we likely need to reintroduce a property on the translator to tell the engine when the source is XA, local transaction, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3948) Provide a different mechanism to update odata wars

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3948?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3948: --------------------------------------- I will carry forward Van's change to master. > Provide a different mechanism to update odata wars > -------------------------------------------------- > > Key: TEIID-3948 > URL: https://issues.jboss.org/browse/TEIID-3948 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > Directly modifying the wars under the base modules is a bad practice. We need to have users modify non-kit artifact files in a different location. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2476) Exclude hidden tables/columns from metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2476?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2476: --------------------------------------- I'm going to start this by first focusing on tables. > Exclude hidden tables/columns from metadata > ------------------------------------------- > > Key: TEIID-2476 > URL: https://issues.jboss.org/browse/TEIID-2476 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > We should offer or possibly default to filtering tables/columns that can not accessed out of the user metadata. This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2476) Exclude hidden tables/columns from metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2476?page=com.atlassian.jira.plugin... ] Work on TEIID-2476 started by Steven Hawkins. --------------------------------------------- > Exclude hidden tables/columns from metadata > ------------------------------------------- > > Key: TEIID-2476 > URL: https://issues.jboss.org/browse/TEIID-2476 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > We should offer or possibly default to filtering tables/columns that can not accessed out of the user metadata. This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3983) External Materialization MATVIEW_ONERROR_ACTION WAIT problem

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3983?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3983: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1309582|https://bugzilla.redhat.com/show_bug.cgi?id=1309582] from NEW to MODIFIED > External Materialization MATVIEW_ONERROR_ACTION WAIT problem > ------------------------------------------------------------ > > Key: TEIID-3983 > URL: https://issues.jboss.org/browse/TEIID-3983 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.5 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > > When using "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT' option in materialized view definition, there's problem with blocked request. > The blocked request is the one, that triggered the materialized view's loading (first query on the defined materialized view). After such request, one can observe, that the query execution doesn't end, but hangs. > Meanwhile while examining the contents of 'status' table in the underlying database, the LoadNumber column's value increases regularly according to the defined ttl. Moreover the 'LOADSTATE' column changes from LOADING to LOADED in similar manner. The materialized table is populated with correct data. From this I assume, materialization is set up correctly. > During the wait, when logging set to DEBUG, there appears regularly, apart from the logs about refreshing the mat view, this entry: > {code:plain} > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 with state PROCESSING > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 - processor blocked > {code} > The log appears in 'ttl' determined intervals, each time after materialized table loading related entries. > The thread mentioned is the one created after the original query execution was initiated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2016