May 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3475) Add a separate example module for embedded examples

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3475?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3475: --------------------------------------- What Kylin is proposing here will add a graphical UI for launching examples and will reorganize them so that the source code is compiled as a teiid maven project - and not by running the example. Van, Ramesh do you have any thoughts? > Add a separate example module for embedded examples > ---------------------------------------------------- > > Key: TEIID-3475 > URL: https://issues.jboss.org/browse/TEIID-3475 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 8.11 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 8.11 > > > Add a separate example module for embedded examples, it will contain a runnable jar, which will load all available examples, it will also contain transaction manager, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3451?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3451: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1214445|https://bugzilla.redhat.com/show_bug.cgi?id=1214445] from NEW to MODIFIED > 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)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-3471: ----------------------------------- > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.7.1.6_2, 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3410) OData object URI does not resolve to a usable URL.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3410?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3410: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1208515 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1208515, https://bugzilla.redhat.com/show_bug.cgi?id=1213584) > OData object URI does not resolve to a usable URL. > -------------------------------------------------- > > Key: TEIID-3410 > URL: https://issues.jboss.org/browse/TEIID-3410 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > OData object URI does not resolve to a usable URL. When accessing a VDB via odata with a browser either via JSON or XML the uri listed in the metadata is not valid, it doesn't have the FQN of the table, only the type shows FQN: > "__metadata" : { > "uri" : "http://localhost:8080/odata/ODataRHQ/rhq_agent(10001)", > "type" : "RHQ32.rhq_agent" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3471: --------------------------------------- In trying to work the array issue TEIID-3436, I get past the metadata error, but still see this behavior when querying through the odata translator against one of our odata services. > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.7.1.6_2, 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3485) Decompose joins only works with a single join

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3485: ------------------------------------- Summary: Decompose joins only works with a single join Key: TEIID-3485 URL: https://issues.jboss.org/browse/TEIID-3485 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins A multi-way join or joins through non-removable view layers cannot currently be decomposed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3484) Decompose join should work with non-ansi joins

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3484?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3484. ----------------------------------- Resolution: Done Updated the planning logic to push criteria prior to decomposing the joins. > Decompose join should work with non-ansi joins > ---------------------------------------------- > > Key: TEIID-3484 > URL: https://issues.jboss.org/browse/TEIID-3484 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > The current logic for RuleDecomposeJoins is only running before rule push criteria, so it needs ansi joins. It should ideally work with non-ansi joins as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3396) Redis Connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3396?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3396: --------------------------------------- I wasn't sure that was official given that all of the infrastructure, project links, etc. was still in place. Also I was able to find our CLAs and this is moot as Devin already completed the process. > Redis Connector > ---------------- > > Key: TEIID-3396 > URL: https://issues.jboss.org/browse/TEIID-3396 > Project: Teiid > Issue Type: Enhancement > Components: Connector API > Affects Versions: 8.11 > Reporter: Devin Pinkston > Assignee: Steven Hawkins > Priority: Minor > > Resource Adapter and Translator for Redis store (http://redis.io/) > Using Jedis client (https://github.com/xetorthio/jedis) > https://github.com/pinkdevelops/teiid -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3396) Redis Connector

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3396?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3396: ------------------------------------- [~shawkins] I think jboss.org removed the restriction to have CLA signed before the contribution is accepted. > Redis Connector > ---------------- > > Key: TEIID-3396 > URL: https://issues.jboss.org/browse/TEIID-3396 > Project: Teiid > Issue Type: Enhancement > Components: Connector API > Affects Versions: 8.11 > Reporter: Devin Pinkston > Assignee: Steven Hawkins > Priority: Minor > > Resource Adapter and Translator for Redis store (http://redis.io/) > Using Jedis client (https://github.com/xetorthio/jedis) > https://github.com/pinkdevelops/teiid -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3484) Decompose join should work with non-ansi joins

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3484: ------------------------------------- Summary: Decompose join should work with non-ansi joins Key: TEIID-3484 URL: https://issues.jboss.org/browse/TEIID-3484 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.11 The current logic for RuleDecomposeJoins is only running before rule push criteria, so it needs ansi joins. It should ideally work with non-ansi joins as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 May 2015