April 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3452) Better highlighting in the query plan when an identified possible issue is seen

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3452?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3452: --------------------------------------- > Can the words "LOW Relational Planner Negation" be rephrased? The logging comes straight from the Annotation entry. They are likely seldom used on the client, but if you do the SHOW ANNOTATIONS, you'd see the same information there broken down in the columns priority, category, annotation, resolution. Ideally this shouldn't be too verbose though as these logs are already quite large. Can you suggest an alternative? As I'd be fine with just adding a pipe or other separator. > The word "LOW" used in the context of the criteria not being pushed down would seem to me to be a possible CRITICAL issue to performance. Anything could be a potential critical performance issue. It's hard to infer that this is a query issue - it's even harder to assume that it's a translator design issue. > Better highlighting in the query plan when an identified possible issue is seen > ------------------------------------------------------------------------------- > > Key: TEIID-3452 > URL: https://issues.jboss.org/browse/TEIID-3452 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.11 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Looking a query plan that's printed in the server log, I see the following line: > "LOW Relational Planner Negation is not supported by source People - People.Person.id < 2 was not pushed" > Can the words "LOW Relational Planner Negation" be rephrased? > The word "LOW" used in the context of the criteria not being pushed down would seem to me to be a possible CRITICAL issue to performance. And I'm not sure most users will claim to know what Relational Planner Negation means and what its implying on an error message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3452) Better highlighting in the query plan when an identified possible issue is seen

by Van Halbert (JIRA)

Van Halbert created TEIID-3452: ---------------------------------- Summary: Better highlighting in the query plan when an identified possible issue is seen Key: TEIID-3452 URL: https://issues.jboss.org/browse/TEIID-3452 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 8.11 Reporter: Van Halbert Assignee: Steven Hawkins Looking a query plan that's printed in the server log, I see the following line: "LOW Relational Planner Negation is not supported by source People - People.Person.id < 2 was not pushed" Can the words "LOW Relational Planner Negation" be rephrased? The word "LOW" used in the context of the criteria not being pushed down would seem to me to be a possible CRITICAL issue to performance. And I'm not sure most users will claim to know what Relational Planner Negation means and what its implying on an error message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3451) OData does not inject schema into queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3451?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3451: --------------------------------------- There are two issues here not caught by TEIID-3358. The insert statement creation is not using the Table full name in the creation of the sql. Also as stated in the issue the fully qualified entity set name is not used for the table lookup - although it was considered to resolve the entityset. > OData does not inject schema into queries > ----------------------------------------- > > Key: TEIID-3451 > URL: https://issues.jboss.org/browse/TEIID-3451 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > OData service does not inject a fully qualified object names for tables for POSTS, PUTs, and DELETEs: > 12:50:34,367 DEBUG [org.teiid.COMMAND_LOG] (http-localhost/127.0.0.1:8080-1) START USER COMMAND: startTime=2015-04-22 12:50:34.367 requestID=XxHTbednhDq7.0 txID=null sessionID=XxHTbednhDq7 applicationName=JDBC principal=teiidUser@teiid-security vdbName=ImsOne vdbVersion=2 sql=INSERT INTO Subscription (SUBSCRIPTION_ID, CLIENT_NAME, DEST_CONNECTION_URI, DEST_SCHEMA_NAME, DEST_TABLE_NAME, PROVIDER_URL, TOPIC_NAME) VALUES (?, ?, ?, ?, ?, ?, ?) > 12:50:34,380 DEBUG [org.teiid.COMMAND_LOG] (http-localhost/127.0.0.1:8080-1) ERROR USER COMMAND: endTime=2015-04-22 12:50:34.379 requestID=XxHTbednhDq7.0 txID=null sessionID=XxHTbednhDq7 principal=teiidUser@teiid-security vdbName=ImsOne vdbVersion=2 finalRowCount=null > 12:50:34,380 WARN [org.teiid.PROCESSOR] (http-localhost/127.0.0.1:8080-1) TEIID30020 Processing exception for request XxHTbednhDq7.0 'Group specified is ambiguous, resubmit the query by fully qualifying the group name: Subscription'. Originally QueryResolverException ResolverUtil.java:814. Enable more detailed logging to see the entire stacktrace. > 12:50:34,383 WARN [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-1) TEIID16012 Could not produce a successful OData response. Returning status ServerErrorException with message Group specified is ambiguous, resubmit the query by fully qualifying the group name: Subscription. > Same insert works fine over JDBC. Offending line from 8.7.0 public github: > https://github.com/teiid/teiid/blob/8.7.x/odata/src/main/java/org/teiid/o... > Note that private Table findTable() on line 925 depends upon org.odata4j.core.EdmEntitySet#getName to return the name, but this is not fully qualified -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3451) OData does not inject schema into queries

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-3451: -------------------------------------- Summary: OData does not inject schema into queries Key: TEIID-3451 URL: https://issues.jboss.org/browse/TEIID-3451 Project: Teiid Issue Type: Bug Components: OData Affects Versions: 8.7 Reporter: Debbie Steigner Assignee: Steven Hawkins OData service does not inject a fully qualified object names for tables for POSTS, PUTs, and DELETEs: 12:50:34,367 DEBUG [org.teiid.COMMAND_LOG] (http-localhost/127.0.0.1:8080-1) START USER COMMAND: startTime=2015-04-22 12:50:34.367 requestID=XxHTbednhDq7.0 txID=null sessionID=XxHTbednhDq7 applicationName=JDBC principal=teiidUser@teiid-security vdbName=ImsOne vdbVersion=2 sql=INSERT INTO Subscription (SUBSCRIPTION_ID, CLIENT_NAME, DEST_CONNECTION_URI, DEST_SCHEMA_NAME, DEST_TABLE_NAME, PROVIDER_URL, TOPIC_NAME) VALUES (?, ?, ?, ?, ?, ?, ?) 12:50:34,380 DEBUG [org.teiid.COMMAND_LOG] (http-localhost/127.0.0.1:8080-1) ERROR USER COMMAND: endTime=2015-04-22 12:50:34.379 requestID=XxHTbednhDq7.0 txID=null sessionID=XxHTbednhDq7 principal=teiidUser@teiid-security vdbName=ImsOne vdbVersion=2 finalRowCount=null 12:50:34,380 WARN [org.teiid.PROCESSOR] (http-localhost/127.0.0.1:8080-1) TEIID30020 Processing exception for request XxHTbednhDq7.0 'Group specified is ambiguous, resubmit the query by fully qualifying the group name: Subscription'. Originally QueryResolverException ResolverUtil.java:814. Enable more detailed logging to see the entire stacktrace. 12:50:34,383 WARN [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-1) TEIID16012 Could not produce a successful OData response. Returning status ServerErrorException with message Group specified is ambiguous, resubmit the query by fully qualifying the group name: Subscription. Same insert works fine over JDBC. Offending line from 8.7.0 public github: https://github.com/teiid/teiid/blob/8.7.x/odata/src/main/java/org/teiid/o... Note that private Table findTable() on line 925 depends upon org.odata4j.core.EdmEntitySet#getName to return the name, but this is not fully qualified -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3434. ----------------------------------- Resolution: Done With TEIID-3444 the teiid_rel:data-ttl property can be set in the model properties as well. Also updated the docs. > Ability to enable/disable caching by table and/or source > -------------------------------------------------------- > > Key: TEIID-3434 > URL: https://issues.jboss.org/browse/TEIID-3434 > Project: Teiid > Issue Type: Feature Request > Reporter: Burak Serdar > Assignee: Steven Hawkins > Fix For: 8.11 > > > We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3436) Add array type support to the odata translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3436?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3436: --------------------------------------- This would appear to take more changes in odata4j - see https://code.google.com/p/odata4j/issues/detail?id=193 The metadata parser only recognizes a collection type when it is used for a function import. Perhaps this should be differed until the v3 or v4 is addressed. > Add array type support to the odata translator > ---------------------------------------------- > > Key: TEIID-3436 > URL: https://issues.jboss.org/browse/TEIID-3436 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > Arrays of basic types in odata responses should be convertible into a runtime array type. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3271) JDBC Translator | Incorrect Update count reported on Batched Update Execution

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3271?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3271: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1214374 > JDBC Translator | Incorrect Update count reported on Batched Update Execution > ----------------------------------------------------------------------------- > > Key: TEIID-3271 > URL: https://issues.jboss.org/browse/TEIID-3271 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Shiveeta Mattoo > Assignee: Steven Hawkins > Labels: Batch-Updates, JDBC-Transator > Fix For: 8.10 > > > Issue is related to Batched updates scenario. > Typically, the executeBatch() returns an array of integers, and each element of the array represents the update count for the respective update statement. > However in case of Teiid JDBC Translator, over and above this, we are processing the array to return a sum of all the elements as in seen in JDBCUpdateExecution -> executeTranslatedCommand method > int[] results = pstatement.executeBatch(); > for (int i=0; i<results.length; i++) { > updateCount += results[i]; > } > The bug is logged to fix this to meet the standard behaviour > Refer thread https://developer.jboss.org/message/914596?et=watches.email.thread#914596 for details -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3444) Add the model properties as extension metadata on the schema

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3444?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3444: --------------------------------------- No, it's now in the correct spot. > Add the model properties as extension metadata on the schema > ------------------------------------------------------------ > > Key: TEIID-3444 > URL: https://issues.jboss.org/browse/TEIID-3444 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > To provide an ability to set extension metadata on the schema we would either need to introduce a new ddl construct or let the existing model property functionality be used. To promote a single mechanism it seems good to let the model properties be injected onto the schema object as extension metadata. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3444) Add the model properties as extension metadata on the schema

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3444?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3444: ------------------------------------- [~shawkins] your doc edit looked like it was at the VDB level properties, here you say model level properties. Am I mis-understanding? > Add the model properties as extension metadata on the schema > ------------------------------------------------------------ > > Key: TEIID-3444 > URL: https://issues.jboss.org/browse/TEIID-3444 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > To provide an ability to set extension metadata on the schema we would either need to introduce a new ddl construct or let the existing model property functionality be used. To promote a single mechanism it seems good to let the model properties be injected onto the schema object as extension metadata. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3444) Add the model properties as extension metadata on the schema

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3444?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3444. ----------------------------------- Resolution: Done Added model properties as extension metadata when the metadatafactory is created. Any manipulation of the metadata object properties will not be reflected in the vdb.xml. > Add the model properties as extension metadata on the schema > ------------------------------------------------------------ > > Key: TEIID-3444 > URL: https://issues.jboss.org/browse/TEIID-3444 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > To provide an ability to set extension metadata on the schema we would either need to introduce a new ddl construct or let the existing model property functionality be used. To promote a single mechanism it seems good to let the model properties be injected onto the schema object as extension metadata. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2015