April 2015 - teiid-issues - Jboss List Archives

[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 reassigned TEIID-3436: ------------------------------------- Assignee: (was: Steven Hawkins) Unassigned until the v3 or v4 is done. > 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 > > 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)

9 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 updated TEIID-3451: ---------------------------------- Fix Version/s: 8.7.1.6_2 > 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 > Fix For: 8.7.1.6_2, 8.11 > > > 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)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3432) support: MongoDB 3.0

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3432?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3432: ------------------------------------- I guess, we could do that. I was wondering if [~ichanjasper] had any issues accessing with new driver? > support: MongoDB 3.0 > --------------------- > > Key: TEIID-3432 > URL: https://issues.jboss.org/browse/TEIID-3432 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.10 > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Fix For: 8.11 > > > According latest documentation for MongoDB 3.0 (Driver Compatibility Changes[1]) the minimum driver version required is 2.13. Currently Teiid 8.10 is using 2.12 > http://docs.mongodb.org/manual/release-notes/3.0-compatibility/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

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

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-3451?page=com.atlassian.jira.plugin... ] Debbie Steigner commented on TEIID-3451: ---------------------------------------- Yes, please add this to 6.2, I've already entered a product bugzilla for this https://bugzilla.redhat.com/show_bug.cgi?id=1214445 > 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 > Fix For: 8.11 > > > 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)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3432) support: MongoDB 3.0

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3432?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3432: --------------------------------------- 2.13.1 is fully api compatible. Should we just go ahead an update the pom for beta1? > support: MongoDB 3.0 > --------------------- > > Key: TEIID-3432 > URL: https://issues.jboss.org/browse/TEIID-3432 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.10 > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Fix For: 8.11 > > > According latest documentation for MongoDB 3.0 (Driver Compatibility Changes[1]) the minimum driver version required is 2.13. Currently Teiid 8.10 is using 2.12 > http://docs.mongodb.org/manual/release-notes/3.0-compatibility/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 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 resolved TEIID-3451. ----------------------------------- Fix Version/s: 8.11 Resolution: Done Corrected the lookup and remaining usage of the type simple name. Do we want this in 62-8.7.x as well? > 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 > Fix For: 8.11 > > > 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)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3453) Add NOT (negation) support for other non-equality sql criteria, example Not Like, Not In, etc.

by Van Halbert (JIRA)

Van Halbert created TEIID-3453: ---------------------------------- Summary: Add NOT (negation) support for other non-equality sql criteria, example Not Like, Not In, etc. Key: TEIID-3453 URL: https://issues.jboss.org/browse/TEIID-3453 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.7.1.6_2, 8.11 Reporter: Van Halbert Assignee: Van Halbert Add NOT (negation) support for when using other non-equality type sql criteria. Example: Not in (1,2,..) or Not like (' '). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3424) infinispan dsl cache translator has disabled capabilities for NE, GT, LT

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3424?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-3424: ---------------------------------- Assignee: Steven Hawkins (was: Van Halbert) > infinispan dsl cache translator has disabled capabilities for NE,GT, LT > ------------------------------------------------------------------------ > > Key: TEIID-3424 > URL: https://issues.jboss.org/browse/TEIID-3424 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2, 8.11 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Documentation states that Infinispan DSL cache translator has this capabilities: Compare Criteria - EQ, NE, LT, GT, LE, GE. > However capabilities for LT, GT and NE are disabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3424) infinispan dsl cache translator has disabled capabilities for NE, GT, LT

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3424?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3424: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/441 > infinispan dsl cache translator has disabled capabilities for NE,GT, LT > ------------------------------------------------------------------------ > > Key: TEIID-3424 > URL: https://issues.jboss.org/browse/TEIID-3424 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2, 8.11 > Reporter: Van Halbert > Assignee: Van Halbert > > Documentation states that Infinispan DSL cache translator has this capabilities: Compare Criteria - EQ, NE, LT, GT, LE, GE. > However capabilities for LT, GT and NE are disabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 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 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)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2015