October 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4367) Fail to deploy VDB with TextTable SELECTOR

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4367?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4367: --------------------------------- Fix Version/s: 8.12.7.6_3 > Fail to deploy VDB with TextTable SELECTOR > ------------------------------------------ > > Key: TEIID-4367 > URL: https://issues.jboss.org/browse/TEIID-4367 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 9.1, 8.12.7.6_3 > > Attachments: texttabvdb-vdb.xml > > > Server fails to deploy dynamic vdb with models which contain following TextTable parameter: SELECTOR. > Server log: > 14:50:56,219 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50030 VDB texttab.1 model "model5" metadata loaded. End Time: 8/1/16 2:50 PM > 14:50:56,220 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50030 VDB texttab.1 model "model3" metadata loaded. End Time: 8/1/16 2:50 PM > 14:50:56,227 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2) TEIID31080 model5.v3 validation error: TEIID31100 Parsing error: Encountered "('a' SELECTOR [*]a[*] COLUMNS y" at line 1, column 40. > Was expecting: <STRINGVAL> > 14:50:56,228 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40073 The metadata for the VDB texttab.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy. > 14:50:56,228 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (teiid-async-threads - 2) TEIID40003 VDB texttab.1 is set to FAILED -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4330) Better planning with chained makedep scenarios

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4330?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-4330. -------------------------------- Resolution: Done > Better planning with chained makedep scenarios > ---------------------------------------------- > > Key: TEIID-4330 > URL: https://issues.jboss.org/browse/TEIID-4330 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.12.7.6_3, 8.7.8.6_2 > > > Plans with an implied series of make dep may not have the hint honored as intended. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4344) OData static context - if resource does not exist then Teiid throws NPE and returns empty page

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4344?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4344: --------------------------------- Fix Version/s: 8.12.7.6_3 > OData static context - if resource does not exist then Teiid throws NPE and returns empty page > ---------------------------------------------------------------------------------------------- > > Key: TEIID-4344 > URL: https://issues.jboss.org/browse/TEIID-4344 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.x > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.1, 8.12.7.6_3 > > > If user requests static resource, which does not exists, Teiid throws NPE and returns empty page. > Example URL: http://localhost:8080/odata4/static/xyz.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4330) Better planning with chained makedep scenarios

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4330?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4330: --------------------------------- Fix Version/s: 8.12.7.6_3 > Better planning with chained makedep scenarios > ---------------------------------------------- > > Key: TEIID-4330 > URL: https://issues.jboss.org/browse/TEIID-4330 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.8.6_2, 8.12.7.6_3 > > > Plans with an implied series of make dep may not have the hint honored as intended. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4330) Better planning with chained makedep scenarios

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4330?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-4330: ---------------------------------- > Better planning with chained makedep scenarios > ---------------------------------------------- > > Key: TEIID-4330 > URL: https://issues.jboss.org/browse/TEIID-4330 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.8.6_2 > > > Plans with an implied series of make dep may not have the hint honored as intended. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4187) Extend support for PI OLEDB Enterprise Queries in OSI PI Translator

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4187?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4187: --------------------------------- Fix Version/s: 8.12.7.6_3 > Extend support for PI OLEDB Enterprise Queries in OSI PI Translator > ------------------------------------------------------------------- > > Key: TEIID-4187 > URL: https://issues.jboss.org/browse/TEIID-4187 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Al S > Assignee: Ramesh Reddy > Fix For: 9.1, 8.12.7.6_3 > > Attachments: PI-OLEDB-Enterprise-2012-User-Guide.pdf > > > Background - PI OLEDB queries go against the PI Data Archive whereas PI OLEDB Enterprise go against PI AF, which is a metadata layer that sits atop the PI Data Archive. Both sets of queries are now accessible from the PI JDBC adapter. > Please add the following enhancements to allow the OSI PI translator to work more effectively with OLEDB Enterprise queries. > 1) Import table valued functions as Teiid procedures > 2) Allow the pushdown of nested table joins > 3) Update the PI translator to use the CROSS APPLY syntax. > 4) When importing schemas, importer.ImportKeys has to be set to false as otherwise we receive a DuplicateRecord exception since the table value function ft_GetPIPoint appears in more than one place in the AF schemas. Could we please put in a fix/workaround to address this? > Please refer to the OLEDB Enterprise Guide for query syntax and rules for more detail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4507) Array index out of bounds exception with anon procedure and update count

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4507: ------------------------------------- Summary: Array index out of bounds exception with anon procedure and update count Key: TEIID-4507 URL: https://issues.jboss.org/browse/TEIID-4507 Project: Teiid Issue Type: Bug Components: JDBC Driver, Query Engine Affects Versions: 8.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1, 9.0.5 If an anon procedure block that does not return a result set is executed and getUpdateCount is called, we'll throw an exception because the update count array will be empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4284) Implement Salesforce Bulk API for SELECTS to Salesforce Connector

by sameer P (JIRA)

[ https://issues.jboss.org/browse/TEIID-4284?page=com.atlassian.jira.plugin... ] sameer P edited comment on TEIID-4284 at 10/12/16 9:15 AM: ----------------------------------------------------------- [~shawkins], I checked the bulk status after the second execution of the same query and it had mainly two bulks : one with the *Not Processed* state (original batch) and the other with *COMPLETED* status (subsequent batch). And from salesforce, the status *Not Processed* means: {code:java} The batch won't be processed. This state is assigned when a job is aborted while the batch is queued. For bulk queries, if the job has PK chunking enabled, this state is assigned to the original batch that contains the query when the subsequent batches are created. After the original batch is changed to this state, you can monitor the subsequent batches and retrieve each batch's results when it's completed. {code} So, may be instead of waiting for just *COMPLETED* status, we should also check the status of subsequent bulks in the Job? was (Author: sameerp): [~shawkins], I checked the bulk status after the second execution of the same query and it had mainly two bulks : one with the *Not Processed* state (main batch) and the other with *COMPLETED* status (subsequent batch). And from salesforce, the status *Not Processed* means: {code:java} The batch won't be processed. This state is assigned when a job is aborted while the batch is queued. For bulk queries, if the job has PK chunking enabled, this state is assigned to the original batch that contains the query when the subsequent batches are created. After the original batch is changed to this state, you can monitor the subsequent batches and retrieve each batch's results when it's completed. {code} So, may be instead of waiting for just *COMPLETED* status, we should also check the status of subsequent bulks in the Job? > Implement Salesforce Bulk API for SELECTS to Salesforce Connector > ----------------------------------------------------------------- > > Key: TEIID-4284 > URL: https://issues.jboss.org/browse/TEIID-4284 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 8.13.5 > Environment: With Salesforce datasource > Reporter: sameer P > Assignee: Steven Hawkins > Fix For: 9.1 > > > There is some huge data (many GBs) in the Salesforce which has around 1.5 million rows and doing some simple select * on it fails with QUERY_TIMEOUT. > The salesforce guys suggested to try Bulk API for select with PK chunking as stated in https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asy... . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4284) Implement Salesforce Bulk API for SELECTS to Salesforce Connector

by sameer P (JIRA)

[ https://issues.jboss.org/browse/TEIID-4284?page=com.atlassian.jira.plugin... ] sameer P commented on TEIID-4284: --------------------------------- [~shawkins], I checked the bulk status after the second execution of the same query and it had mainly two bulks : one with the *Not Processed* state (main batch) and the other with *COMPLETED* status (subsequent batch). And from salesforce, the status *Not Processed* means: {code:java} The batch won't be processed. This state is assigned when a job is aborted while the batch is queued. For bulk queries, if the job has PK chunking enabled, this state is assigned to the original batch that contains the query when the subsequent batches are created. After the original batch is changed to this state, you can monitor the subsequent batches and retrieve each batch's results when it's completed. {code} So, may be instead of waiting for just *COMPLETED* status, we should also check the status of subsequent bulks in the Job? > Implement Salesforce Bulk API for SELECTS to Salesforce Connector > ----------------------------------------------------------------- > > Key: TEIID-4284 > URL: https://issues.jboss.org/browse/TEIID-4284 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 8.13.5 > Environment: With Salesforce datasource > Reporter: sameer P > Assignee: Steven Hawkins > Fix For: 9.1 > > > There is some huge data (many GBs) in the Salesforce which has around 1.5 million rows and doing some simple select * on it fails with QUERY_TIMEOUT. > The salesforce guys suggested to try Bulk API for select with PK chunking as stated in https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asy... . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4187) Extend support for PI OLEDB Enterprise Queries in OSI PI Translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4187?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4187: ------------------------------------- [~jolee] Yes TEIID-4202 is required for this. > Extend support for PI OLEDB Enterprise Queries in OSI PI Translator > ------------------------------------------------------------------- > > Key: TEIID-4187 > URL: https://issues.jboss.org/browse/TEIID-4187 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Al S > Assignee: Ramesh Reddy > Fix For: 9.1 > > Attachments: PI-OLEDB-Enterprise-2012-User-Guide.pdf > > > Background - PI OLEDB queries go against the PI Data Archive whereas PI OLEDB Enterprise go against PI AF, which is a metadata layer that sits atop the PI Data Archive. Both sets of queries are now accessible from the PI JDBC adapter. > Please add the following enhancements to allow the OSI PI translator to work more effectively with OLEDB Enterprise queries. > 1) Import table valued functions as Teiid procedures > 2) Allow the pushdown of nested table joins > 3) Update the PI translator to use the CROSS APPLY syntax. > 4) When importing schemas, importer.ImportKeys has to be set to false as otherwise we receive a DuplicateRecord exception since the table value function ft_GetPIPoint appears in more than one place in the AF schemas. Could we please put in a fix/workaround to address this? > Please refer to the OLEDB Enterprise Guide for query syntax and rules for more detail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2016