May 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3468) Exception with same table name in materialization procedures

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3468?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3468. ----------------------------------- Resolution: Done Updated the sysadmin sql and ensured there's escaping of the literals used in the materializationmanager. > Exception with same table name in materialization procedures > ------------------------------------------------------------ > > Key: TEIID-3468 > URL: https://issues.jboss.org/browse/TEIID-3468 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > The sql defining the mat view procedures is not qualifying the reference to the schemaName, and throwing an exception when the scalar subquery returns more than 1 value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3468) Exception with same table name in materialization procedures

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3468: ------------------------------------- Summary: Exception with same table name in materialization procedures Key: TEIID-3468 URL: https://issues.jboss.org/browse/TEIID-3468 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.5 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.11 The sql defining the mat view procedures is not qualifying the reference to the schemaName, and throwing an exception when the scalar subquery returns more than 1 value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3463) Add an importer for LDAP

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3463?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3463: ---------------------------------- Adding the link to the sf ticket. It's still in flux as to what exactly will be needed. > Add an importer for LDAP > ------------------------ > > Key: TEIID-3463 > URL: https://issues.jboss.org/browse/TEIID-3463 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Attachments: ldap-ds-1.png, ldap-ds-2.png, ldap-ds-3.png > > > Related to TEIIDDES-2499, Teiid should add import support for LDAP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3039) Add support for odata expand

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3039?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3039: ------------------------------------- I would prefer we do this work in V4, as spec is much more detailed about it here. Also gives us option to move users from V2 to V4. There is also "aggregations" extension to odata, we may have to get to after 8.11 As per the filtering, it can be on the expanded item like {code} http://host/service.svc/Customers?$expand=Orders($filter=Amount gt 100) {code} it can be multiple documents like (even nested) {code} http://host/service.svc/Orders?$expand=Items($expand=Product),Customer {code} or recursive {code} http://contoso.com/HR/Employees?$expand=Model.Manager/DirectReports($leve... {code} see this for more info [http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr...] > Add support for odata expand > ---------------------------- > > Key: TEIID-3039 > URL: https://issues.jboss.org/browse/TEIID-3039 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Fix For: 8.12 > > > We should add support for odata expand. This can be done with logic similar to the xml document model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3465) mongoDB: Update Metadata processor to handle nested documents

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3465?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3465. --------------------------------- Labels: Beta2 (was: ) Fix Version/s: 8.11 Resolution: Done Fixing the import for nested tables to be represented correctly > mongoDB: Update Metadata processor to handle nested documents > ------------------------------------------------------------- > > Key: TEIID-3465 > URL: https://issues.jboss.org/browse/TEIID-3465 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.10 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta2 > Fix For: 8.11 > > > Teiid 8.10 version provided a detailed support for the nested documents in MongoDB based on the schema and extension properties provided. > However when reading the existing JSON documents from MongoDB to figure out the compatible schema, it is not updated to recognize all the possible nesting in JSON document to produce a correct schema. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 commented on TEIID-3442: --------------------------------------- It seems like 1 is a straight-forward option for now. There are only a couple cases outlined in the programming guide for which we'd want to consider adding a an additional translator type for workarounds. > 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: Open To Community > > 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, 11 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: --------------------------------------- The first commit from TEIID-3358 bc27b9a > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3039) Add support for odata expand

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3039?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3039: --------------------------------------- Should we start implementing this for v2 just so that we have something ready with 8.11 for inclusion in the product? I don't recall seeing anything in the spec that looks like context criteria for referenced entity filtering. Is all filtering effectively on the root entity? > Add support for odata expand > ---------------------------- > > Key: TEIID-3039 > URL: https://issues.jboss.org/browse/TEIID-3039 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Fix For: 8.12 > > > We should add support for odata expand. This can be done with logic similar to the xml document model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3429) Provide hooks to interrogate metadata prior to full import

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3429?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3429: --------------------------------------- Let's hear from the Designer team on this also. It it enough to just expose select metadata procedures? Or do you need to see something else such as just setting more defaults (possibly on the Teiid side) when creating sources (strongly recommend import schema to be specified for JDBC import for example)? > Provide hooks to interrogate metadata prior to full import > ----------------------------------------------------------- > > Key: TEIID-3429 > URL: https://issues.jboss.org/browse/TEIID-3429 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > To support the Desinger we should offer the ability to interrogate metadata prior to full import. > Exploring metadata is effectively an entirely different mode of operation with respect to the current metadata processing logic on the Teiid side. Also partial metadata isn't something that would neatly be expressed through DDL - tables without columns, a list of schema names, etc. > Ways around that would be to expose source procedures for metadata interrogation: > > getTableNames - which would probably give both the Teiid name and the name in source and consider the current translator metadata settings > getProcedureNames > And importer specific info such as for JDBC getTableTypes, getCatalogNames, getSchemaNames > > I'd want to keep it fairly high level though. Getting column or key information I'd expect would be done through the normal full import. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3467) expose bufferserviceimpl for configuration of buffermanager in embedded

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3467: ------------------------------------- Summary: expose bufferserviceimpl for configuration of buffermanager in embedded Key: TEIID-3467 URL: https://issues.jboss.org/browse/TEIID-3467 Project: Teiid Issue Type: Feature Request Components: Embedded Reporter: Steven Hawkins Assignee: Steven Hawkins We have a few configuration options exposed on the embeddedconfiguration related to the buffer manager, but should also look at exposing more. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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