January 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3899) Allow Web Services translator to retrieve metadata without source connection

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3899?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3899: --------------------------------------- Sorry I didn't see the full scope of what you were doing with the doc change. I saw that the source related methods, weren't documented and added them to https://docs.jboss.org/author/display/TEIID/Translator+Capabilities We'll add back the doc change you had for the execution property if we need that. It also may make sense to just switch the source required for metadata flag back to false and keep the nativemetadatarepository change. > Allow Web Services translator to retrieve metadata without source connection > ---------------------------------------------------------------------------- > > Key: TEIID-3899 > URL: https://issues.jboss.org/browse/TEIID-3899 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.11 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.13, 8.12.x > > > The "ws" translator, is set to "isSourceRequiredForMetadata" to true. However, there are two issues > 1) There is no way to turn this flag to false > 2) If the "ws" translator is secured through "security-domain", then authentication failure message by passes the "isSourceRequiredForMetadata" flag and returns as error, thus leaving the VDB in "metadata load failed" state. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3899) Allow Web Services translator to retrieve metadata without source connection

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3899?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3899: --------------------------------------- > There is no way to turn this flag to false Is there a circumstance where you can retrieve the metadata without a source connection? > If the "ws" translator is secured through "security-domain", then authentication failure message by passes the "isSourceRequiredForMetadata" flag and returns as error, thus leaving the VDB in "metadata load failed" state. We probably need to allow for models to have a management/metadata specific connection factories specified, rather than always assuming that the data connections can be used. Would that work in this case? > Allow Web Services translator to retrieve metadata without source connection > ---------------------------------------------------------------------------- > > Key: TEIID-3899 > URL: https://issues.jboss.org/browse/TEIID-3899 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.11 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.13, 8.12.x > > > The "ws" translator, is set to "isSourceRequiredForMetadata" to true. However, there are two issues > 1) There is no way to turn this flag to false > 2) If the "ws" translator is secured through "security-domain", then authentication failure message by passes the "isSourceRequiredForMetadata" flag and returns as error, thus leaving the VDB in "metadata load failed" state. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3899) Allow Web Services translator to retrieve metadata without source connection

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3899: ----------------------------------- Summary: Allow Web Services translator to retrieve metadata without source connection Key: TEIID-3899 URL: https://issues.jboss.org/browse/TEIID-3899 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.11 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.13, 8.12.x The "ws" translator, is set to "isSourceRequiredForMetadata" to true. However, there are two issues 1) There is no way to turn this flag to false 2) If the "ws" translator is secured through "security-domain", then authentication failure message by passes the "isSourceRequiredForMetadata" flag and returns as error, thus leaving the VDB in "metadata load failed" state. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

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

by Don Krapohl (JIRA)

Don Krapohl created TEIID-3898: ---------------------------------- Summary: 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 Assignee: Steven Hawkins 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)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3897) dimensional check for ewkb is incorrect

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3897: ------------------------------------- Summary: dimensional check for ewkb is incorrect Key: TEIID-3897 URL: https://issues.jboss.org/browse/TEIID-3897 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.11 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.13, 8.12.4 The geometry logic to prevent ewkb from being used is looking for the number of dimensions to be greater than 2 - this will never be the case with jts. We should be looking instead at the coorinates for the z value. A similar check is needed when just wkt is expected and not ewkt. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3896) When error occurs in the materialization process, an ERROR should be logged instead of DEBUG

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3896?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3896: ------------------------------------ I just confirmed that Stock wasn't being fully qualified. I tested that theory by removing the other models that were not needed, but had Stock table, and was able to get past this issue. > When error occurs in the materialization process, an ERROR should be logged instead of DEBUG > -------------------------------------------------------------------------------------------- > > Key: TEIID-3896 > URL: https://issues.jboss.org/browse/TEIID-3896 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.12.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Minor > > When trying to do materialization, there's an issue (DEBUG) appearing in the server.log: > 09:58:51,272 DEBUG [org.teiid.PROCESSOR] (Worker5_QueryProcessorQueue302) org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due to: Group specified is ambiguous, resubmit the query by fully qualifying the group name: Stock > I believe this be logged as an ERROR as it appears to be detrimental to what's being materialized. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3896) When error occurs in the materialization process, an ERROR should be logged instead of DEBUG

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3896?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3896: --------------------------------------- > Also, what is this error telling me that's wrong so that I can correct it? MatViewTable is likely being referred to as just Stock, and there are multiple tables/views with the simple name Stock. > It appears that this issue is triggering the updating of the status table to "FAILED_LOAD". Since it fails to do the insert you would expect that the load would fail. > When error occurs in the materialization process, an ERROR should be logged instead of DEBUG > -------------------------------------------------------------------------------------------- > > Key: TEIID-3896 > URL: https://issues.jboss.org/browse/TEIID-3896 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.12.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Minor > > When trying to do materialization, there's an issue (DEBUG) appearing in the server.log: > 09:58:51,272 DEBUG [org.teiid.PROCESSOR] (Worker5_QueryProcessorQueue302) org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due to: Group specified is ambiguous, resubmit the query by fully qualifying the group name: Stock > I believe this be logged as an ERROR as it appears to be detrimental to what's being materialized. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3896) When error occurs in the materialization process, an ERROR should be logged instead of DEBUG

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3896?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3896: ------------------------------------ Also, what is this error telling me that's wrong so that I can correct it? It appears that this issue is triggering the updating of the status table to "FAILED_LOAD". > When error occurs in the materialization process, an ERROR should be logged instead of DEBUG > -------------------------------------------------------------------------------------------- > > Key: TEIID-3896 > URL: https://issues.jboss.org/browse/TEIID-3896 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.12.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Minor > > When trying to do materialization, there's an issue (DEBUG) appearing in the server.log: > 09:58:51,272 DEBUG [org.teiid.PROCESSOR] (Worker5_QueryProcessorQueue302) org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due to: Group specified is ambiguous, resubmit the query by fully qualifying the group name: Stock > I believe this be logged as an ERROR as it appears to be detrimental to what's being materialized. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3896) When error occurs in the materialization process, an ERROR should be logged instead of DEBUG

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3896?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3896: --------------------------------------- Generally error is for system issues, so we can look at targeting this to the warn level. > When error occurs in the materialization process, an ERROR should be logged instead of DEBUG > -------------------------------------------------------------------------------------------- > > Key: TEIID-3896 > URL: https://issues.jboss.org/browse/TEIID-3896 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.12.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Minor > > When trying to do materialization, there's an issue (DEBUG) appearing in the server.log: > 09:58:51,272 DEBUG [org.teiid.PROCESSOR] (Worker5_QueryProcessorQueue302) org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due to: Group specified is ambiguous, resubmit the query by fully qualifying the group name: Stock > I believe this be logged as an ERROR as it appears to be detrimental to what's being materialized. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3896) When error occurs in the materialization process, an ERROR should be logged instead of DEBUG

by Van Halbert (JIRA)

Van Halbert created TEIID-3896: ---------------------------------- Summary: When error occurs in the materialization process, an ERROR should be logged instead of DEBUG Key: TEIID-3896 URL: https://issues.jboss.org/browse/TEIID-3896 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 8.12.2 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor When trying to do materialization, there's an issue (DEBUG) appearing in the server.log: 09:58:51,272 DEBUG [org.teiid.PROCESSOR] (Worker5_QueryProcessorQueue302) org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due to: Group specified is ambiguous, resubmit the query by fully qualifying the group name: Stock I believe this be logged as an ERROR as it appears to be detrimental to what's being materialized. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016