November 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2973) Switch OData support to Olingo

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2973?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2973: -------------------------------- Fix Version/s: 8.10 (was: 8.9) > Switch OData support to Olingo > ------------------------------ > > Key: TEIID-2973 > URL: https://issues.jboss.org/browse/TEIID-2973 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors, OData > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.10 > > > Whenever an olingo final is available for odata 3/4 we'll want to switch our support to utilize that. The best guess now is that this will happen in the 8.9 timeframe. Additional support can then be added for later odata features, which will have subtasks as necessary. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3222) Dependent join planning modifies left outer to inner join

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3222?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3222. ----------------------------------- Resolution: Done The joinutil optimize join type call was not accounted for in modifying lower level joins in dependent join planning. Added additional checks. > Dependent join planning modifies left outer to inner join > --------------------------------------------------------- > > Key: TEIID-3222 > URL: https://issues.jboss.org/browse/TEIID-3222 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.9 > > > When planning a dependent join with a nested left outer join, the left outer join can get modified to an inner join inappropriately. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3222) Dependent join planning modifies left outer to inner join

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3222: ------------------------------------- Summary: Dependent join planning modifies left outer to inner join Key: TEIID-3222 URL: https://issues.jboss.org/browse/TEIID-3222 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Blocker Fix For: 8.9 When planning a dependent join with a nested left outer join, the left outer join can get modified to an inner join inappropriately. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2903) Dynamic VDB with Google Spreadsheet source - no metadata

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2903?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2903: ------------------------------------------------ Julian Coleman <jcoleman(a)redhat.com> changed the Status of [bug 1109421|https://bugzilla.redhat.com/show_bug.cgi?id=1109421] from MODIFIED to ON_QA > Dynamic VDB with Google Spreadsheet source - no metadata > --------------------------------------------------------- > > Key: TEIID-2903 > URL: https://issues.jboss.org/browse/TEIID-2903 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Steven Hawkins > Fix For: 8.7, 8.4.4 > > > Deployed Dynamic VDB with Google Spreadsheet source. This is in the server log: > 16:17:49,286 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2) TEIID31070 Empty model;There are no tables, procedures or functions defined in this model importVDBSrcModel > According to the translator docs https://docs.jboss.org/author/display/TEIID/Google+Spreadsheet+Translator "There are no google-spreadsheet importer settings, but it does provide metadata for dynamic VDBs." > No metadata is returned. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2831) Add a full ddl example to the ldap translator docs

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-2831?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-2831: ------------------------------------ I have added a full ddl ldap-as-a-datasource quickstart, also updated the Ref Guide added a Usage section, which show how use ldap translator extract users under HR Gruop in OpenLDAP server. [1] https://github.com/teiid/teiid-quickstarts/tree/master/ldap-as-a-datasource [2] https://docs.jboss.org/author/display/TEIID/LDAP+Translator > Add a full ddl example to the ldap translator docs > -------------------------------------------------- > > Key: TEIID-2831 > URL: https://issues.jboss.org/browse/TEIID-2831 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Kylin Soong > > It would be helpful to have a full example of LDAP metadata. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3202) Add the translator to the log entry when the model is loaded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3202?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3202. ----------------------------------- Resolution: Done Added a new log prior to the load that indicates the translator name / connection. There may not be a single translator in the case of multi-source. And a user may have to refer back to the vdb in any case with overriden translators. > Add the translator to the log entry when the model is loaded > ------------------------------------------------------------ > > Key: TEIID-3202 > URL: https://issues.jboss.org/browse/TEIID-3202 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Optional > Fix For: 8.10 > > > When the server starts up and there's a log entry for the model when its loaded. Example: > 11:00:29,691 INFO [org.teiid.RUNTIME] (MSC service thread 1-2) TEIID50029 VDB QT_Hive_Push.1 model "Source" metadata is currently being loaded. Start Time: 9/25/14 11:00 AM > It would be nice to have the associated translator that was assigned at load time. This can be helpful to tracking down issues. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3163) Add TEXTTABLE capability to support Custom Line Separator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3163?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3163. ----------------------------------- Resolution: Done Added support for the ROW DELIMITER option on TEXTTABLE (no corresponding functionality yet for textagg). Updated the docs and added a release note as well. > Add TEXTTABLE capability to support Custom Line Separator > ---------------------------------------------------------- > > Key: TEIID-3163 > URL: https://issues.jboss.org/browse/TEIID-3163 > Project: Teiid > Issue Type: Enhancement > Environment: Teiid 8.8.0.Final > Reporter: Shiveeta Mattoo > Assignee: Steven Hawkins > Labels: FileConnector, TEXTTABLE > Fix For: 8.10 > > > Add TEXTTABLE capability to support Custom Line Separator -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3221) Add UI support for TEXTTABLE Custom Line Separator

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3221: ------------------------------------- Summary: Add UI support for TEXTTABLE Custom Line Separator Key: TEIID-3221 URL: https://issues.jboss.org/browse/TEIID-3221 Project: Teiid Issue Type: Enhancement Environment: Teiid 8.8.0.Final Reporter: Shiveeta Mattoo Assignee: Steven Hawkins Fix For: 8.10 Add TEXTTABLE capability to support Custom Line Separator -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3192) Migrate Salesforce connectivity to sf partner api jars

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3192?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3192: --------------------------------------- That flow is not part of the api from what I can see. Of course it looks like you can just use a token for authentication. > Migrate Salesforce connectivity to sf partner api jars > ------------------------------------------------------ > > Key: TEIID-3192 > URL: https://issues.jboss.org/browse/TEIID-3192 > Project: Teiid > Issue Type: Component Upgrade > Components: Salesforce Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > There are several deficiencies in using CXF for salesforce connectivity - we are not batching correctly, there is additional CXF overhead, and we have to maintain our own generated java of the api. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3215) External Materialization ON_VDB_START_SCRIPT invocation issues

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3215?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3215: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1163685|https://bugzilla.redhat.com/show_bug.cgi?id=1163685] from NEW to MODIFIED > External Materialization ON_VDB_START_SCRIPT invocation issues > -------------------------------------------------------------- > > Key: TEIID-3215 > URL: https://issues.jboss.org/browse/TEIID-3215 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > Labels: Final > Fix For: 8.7.1, 8.9 > > > With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.) > Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does. > A - 1. Copy the vdbname-vdb.xml into deployments folder > 2. Start the server > B - 1. Start the server > 2. Copy the vdbname-vdb.xml into deployments folder > That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table natively,...) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2014