June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3518) Add a print method for Virtual Procedures

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3518?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3518. ----------------------------------- Resolution: Duplicate Issue See the system procedures SYSADMIN.logMsg SYSADMIN.isLoggable https://docs.jboss.org/author/display/TEIID/System+Procedures > Add a print method for Virtual Procedures > ----------------------------------------- > > Key: TEIID-3518 > URL: https://issues.jboss.org/browse/TEIID-3518 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.11 > Reporter: Kylin Soong > Assignee: Steven Hawkins > > Add a function that Virtual Procedures can print line, like DBMS_OUTPUT.PUT_LINE in Oracle, this is useful for debug the Procedures. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3518) Add a print method for Virtual Procedures

by Kylin Soong (JIRA)

Kylin Soong created TEIID-3518: ---------------------------------- Summary: Add a print method for Virtual Procedures Key: TEIID-3518 URL: https://issues.jboss.org/browse/TEIID-3518 Project: Teiid Issue Type: Feature Request Affects Versions: 8.11 Reporter: Kylin Soong Assignee: Steven Hawkins Add a function that Virtual Procedures can print line, like DBMS_OUTPUT.PUT_LINE in Oracle, this is useful for debug the Procedures. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3510) Move the Embedded examples into separate repository

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3510?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3510: ------------------------------------ > I do not think we need a "common" module "common" module used to hold EmbeddedHelper which expose ironjacamar/narayana for transaction manager, this is needed for all examples, I also prepare add more functionality in this module future, 'org.teiid.example.JDBCUtils' also under this module. > Move the Embedded examples into separate repository > ---------------------------------------------------- > > Key: TEIID-3510 > URL: https://issues.jboss.org/browse/TEIID-3510 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 8.11 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 8.11 > > > Create a separate repository for embedded examples, define a maven BOM file for the dependencies management of all examples, and prepare for further refinement like add xa datasources support, add OAuth/REST service, etc. -- 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 commented on TEIID-3410: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1208515|https://bugzilla.redhat.com/show_bug.cgi?id=1208515] from ASSIGNED to ON_QA > 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 > Fix For: 8.11 > > > 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-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 Update: (was: Perform) Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=1208515) > 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 > Fix For: 8.11 > > > 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-3358) Issues with entity set names

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3358: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1208515|https://bugzilla.redhat.com/show_bug.cgi?id=1208515] from ASSIGNED to ON_QA > Issues with entity set names > ---------------------------- > > Key: TEIID-3358 > URL: https://issues.jboss.org/browse/TEIID-3358 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.7.1.6_2, 8.11, 8.7.3 > > > The entity set name used for sql generation should be the fully qualified name. If there is for example two table with the same names in schemas visible to odata, but one of the tables does not have a key, then an ambiguous name exception will be thrown if an odata url is used with only the base table name. > It also appears that the URI link in the results metadata uses the non-qualified table name, which will have issues in the scenario above. > We may also need to document or add an additional check for ambiguity as the OData4j findEdmEntitySet logic will return the first matching entity, which is generally against our approach to resolving. -- 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 Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3410?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3410. ----------------------------------- Fix Version/s: 8.11 Resolution: Done Address the Atom feed as well with oreva 0.8.6 > 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 > Fix For: 8.11 > > > 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-3442) Apache Spark support via SparkSQL and DataFrames

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3442?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3442: ---------------------------------- Fix Version/s: 8.12 (was: Open To Community) > Apache Spark support via SparkSQL and DataFrames > ------------------------------------------------ > > Key: TEIID-3442 > URL: https://issues.jboss.org/browse/TEIID-3442 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.10 > Reporter: John Muller > Labels: Connectors, Spark, Translators > Fix For: 8.12 > > Original Estimate: 20 weeks > Remaining Estimate: 20 weeks > > Eliciting comments for Apache Spark support. With the release of Panda's like DataFrames, it is a little more feasible to directly translate to SparkSQL: > https://spark.apache.org/docs/latest/sql-programming-guide.html > Options in order of complexity: > 1. Use the existing Hive connector / translator. Spark still uses the Hive metastore. > 2. Thrift JDBC driver. This is what Microstrategy, Tableau, QlikView and others use, most rudimentary API for accessing Spark. > 3. Native SparkSQL via building Spark jobs and submitting them to a running Spark driver. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3480) External Materialization status

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3480?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3480: ---------------------------------- Fix Version/s: 8.12 > External Materialization status > ------------------------------- > > Key: TEIID-3480 > URL: https://issues.jboss.org/browse/TEIID-3480 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.12 > > > When external materialization is configured with "STATUS" table, then Teiid should expose those stats over CLI and in the web-console. Currently the internal materialization does show status, need to expand to the external matviews. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 updated TEIID-3436: ---------------------------------- Fix Version/s: 8.12 > 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: Ramesh Reddy > Fix For: 8.12 > > > 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, 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 June 2015