October 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4204) Examples dynamicvdb-restservice - rest client returns always empty body

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4204?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4204. ----------------------------------- Resolution: Rejected I concur with Kylin that this is working. You have to follow all of the pre-reqs though and there is a potential issue if you already have marketdata-file resource adapter, which can initially be pointed to the wrong data directory that can result in an empty response. > Examples dynamicvdb-restservice - rest client returns always empty body > ------------------------------------------------------------------------ > > Key: TEIID-4204 > URL: https://issues.jboss.org/browse/TEIID-4204 > Project: Teiid > Issue Type: Bug > Components: Quick Starts > Affects Versions: 8.12.5 > Reporter: Van Halbert > Assignee: Kylin Soong > Priority: Minor > Fix For: 9.1 > > > Description of problem: > rest-client returns always empty body for every request like follows: > [jdurani@localhost resteasy-client]$ java -cp target/dependency/*:target/dynamicvdb-resteasy-client.jar org.jboss.teiid.quickstart.PortfolioClient > JAX-RS 2.0 Client API -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4502) Remove references to deprecated UseConnectorMetadata in docs/examples

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4502: ------------------------------------- Summary: Remove references to deprecated UseConnectorMetadata in docs/examples Key: TEIID-4502 URL: https://issues.jboss.org/browse/TEIID-4502 Project: Teiid Issue Type: Quality Risk Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1 There are still lingering references to UseConnectorMetadata that should be replaced with the relevant usage of cache-metadata -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4501) Salesforce 34 resource adapter should default to the 34 api

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4501?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4501: --------------------------------------- If there are no objections, I think this should go into 9.1/9.0 as well. > Salesforce 34 resource adapter should default to the 34 api > ----------------------------------------------------------- > > Key: TEIID-4501 > URL: https://issues.jboss.org/browse/TEIID-4501 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > The salesforce-34 resource adapter ra.xml still points to the 22 api url by default. It should point to 34. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4501) Salesforce 34 resource adapter should default to the 34 api

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4501: ------------------------------------- Summary: Salesforce 34 resource adapter should default to the 34 api Key: TEIID-4501 URL: https://issues.jboss.org/browse/TEIID-4501 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.12 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.2 The salesforce-34 resource adapter ra.xml still points to the 22 api url by default. It should point to 34. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4284?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4284: --------------------------------------- > Aah I did not get where exactly is that. Is that in your Junit test cases Steven? No I mean adapt https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asy... directly to confirm that Teiid's behavior is the same. > with the above stated statements in the Log and does not come out at all for the second query What do you mean by second query? > 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)

9 years, 5 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/10/16 1:26 PM: ----------------------------------------------------------- And, I also tried on a small table with some 60 rows and the result is same. That is, it returns results on first query and it continuously generates requests (which I believe is the usage of Bulk API) with the above stated statements in the Log and does not come out at all for the second query. was (Author: sameerp): And, I also tried on a small table with some 60 rows and the result is same. That is, it returns results on first query and it continuously generates requests (which I believe is the usage of Bulk API) with the above stated statements in the Log and does not come out at all. > 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)

9 years, 5 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: --------------------------------- And, I also tried on a small table with some 60 rows and the result is same. That is, it returns results on first query and it continuously generates requests (which I believe is the usage of Bulk API) with the above stated statements in the Log and does not come out at all. > 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)

9 years, 5 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: --------------------------------- The table has around 1.5 million rows and the size is around some GBs. > Would it be possible for you to adapt the salesforce asynch example to run directly against your scenario to confirm that Teiid is not introducing anything unexpected? Comment Aah I did not get where exactly is that. Is that in your Junit test cases Steven? > 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)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4469) Insert with query expression does not apply source hint to target

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4469?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4469: --------------------------------------- You are seeing an error in the backport. It looks like not all of the insert cases have the source hint associated. Your scenario should work on master/9.1 > Insert with query expression does not apply source hint to target > ----------------------------------------------------------------- > > Key: TEIID-4469 > URL: https://issues.jboss.org/browse/TEIID-4469 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1.6_2 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.5, 8.7.10_6.2 > > Attachments: oracledba-vdb.xml > > > "INSERT INTO ... SELECT ..." statements result in a ProjectIntoNode which seems to prevent any source hints from being passed down to the relevant source. These work correctly with an "INSERT INTO ... VALUES ..." statement. I've included example user and final query plan data below for the non-working [1] and working [2] insert statements. > [1] source hint not applied to ProjectIntoNode: > USER COMMAND: > INSERT /*+sh test:'append' */ INTO test.TEST (ID, "VALUE") SELECT X.id AS ID, X."value" AS "VALUE" FROM (SELECT bqt.SMALLA.INTKEY AS id, bqt.SMALLA.INTNUM AS "value" FROM bqt.SMALLA WHERE bqt.SMALLA.INTKEY = 0) AS X > ... > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > ProjectIntoNode(0) output=[Count] test.TEST > AccessNode(1) output=[bqt.SMALLA.INTKEY AS ID, bqt.SMALLA.INTNUM AS "VALUE"] SELECT /*+sh test:'append' */ g_0.INTKEY, g_0.INTNUM FROM bqt.SMALLA AS g_0 WHERE g_0.INTKEY = 0 > [2] source hint applied to AccessNode: > USER COMMAND: > INSERT /*+sh test:'append' */ INTO test.TEST (ID, "VALUE") VALUES ('-1', '-1') > ... > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > AccessNode(0) output=[Count] INSERT /*+sh test:'append' */ INTO test.TEST (ID, "VALUE") VALUES ('-1', '-1') -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4284?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4284: --------------------------------------- What table sizes are you dealing with? Would it be possible for you to adapt the salesforce asynch example to run directly against your scenario to confirm that Teiid is not introducing anything unexpected? > 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)

9 years, 5 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 October 2016