October 2016 - teiid-issues - Jboss List Archives

[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: --------------------------------- I mean to say when I do the same query second time. > 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. Yes will check that. Thanks. > 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-4489) Adjust defaults and use of 1 to 10 data sources to recommend the SMALL size

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4489?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4489: ------------------------------------------- Bugzilla Update: Perform > Adjust defaults and use of 1 to 10 data sources to recommend the SMALL size > --------------------------------------------------------------------------- > > Key: TEIID-4489 > URL: https://issues.jboss.org/browse/TEIID-4489 > Project: Teiid > Issue Type: Enhancement > Components: Sizing Application > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Kylin Soong > > Based on recommendations: > small : 16 cores, with at least 32 GB RAM. 2 DV instances. (small means may be 5 ~10 sources, rows into millions, YMMV) > medium : 32 cores with 64 GB RAM, 4 DV instances. (medium means may be 10 ~ 20 sources, rows into multi-millions, YMMV) > Large: custom > The defaults in the sizing applications, along with selecting 1 to 10 data sources, should result in the SMALL recommendation. It should be clear to indicate the number of instances and the size recommendation per instance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3825) Add a wildfly-swarm-teiid Fraction for running teiid as an uberjar

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3825?page=com.atlassian.jira.plugin... ] Work on TEIID-3825 started by Kylin Soong. ------------------------------------------ > Add a wildfly-swarm-teiid Fraction for running teiid as an uberjar > ------------------------------------------------------------------ > > Key: TEIID-3825 > URL: https://issues.jboss.org/browse/TEIID-3825 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 9.0 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.2 > > > Fractions within WildFly Swarm are roughly equivalent to subsystems within WildFly, we have teiid subsystem in Server mode, so I think a Fraction is necessary to run teiid with Swarm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3825) Add a wildfly-swarm-teiid Fraction for running teiid as an uberjar

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3825?page=com.atlassian.jira.plugin... ] Kylin Soong updated TEIID-3825: ------------------------------- Description: Fractions within WildFly Swarm are roughly equivalent to subsystems within WildFly, we have teiid subsystem in Server mode, so I think a Fraction is necessary to run teiid with Swarm. was: Fractions within WildFly Swarm are roughly equivalent to subsystems within WildFly, we have teiid subsystem in Server mode, so I think a Fraction is necessary to run teiid with Swarm. ||Task||Status||Note|| |Teiid feature pack |Pending |in high priority, faction develop and modules generation depend on this | |Config api |Done |N/A| |Fraction Dev |Pending | this block on feature pack | |Modules(translator and connector) |Pending |n/a | |Examples and Documents |Pending |n/a | Fix Version/s: 9.2 (was: 9.x) > Add a wildfly-swarm-teiid Fraction for running teiid as an uberjar > ------------------------------------------------------------------ > > Key: TEIID-3825 > URL: https://issues.jboss.org/browse/TEIID-3825 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 9.0 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.2 > > > Fractions within WildFly Swarm are roughly equivalent to subsystems within WildFly, we have teiid subsystem in Server mode, so I think a Fraction is necessary to run teiid with Swarm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4453) Update database logging to semantic versioning and logoninfo

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4453?page=com.atlassian.jira.plugin... ] Kylin Soong resolved TEIID-4453. -------------------------------- Resolution: Done Pull request(https://github.com/teiid/teiid-extensions/pull/50) be merged. > Update database logging to semantic versioning and logoninfo > ------------------------------------------------------------ > > Key: TEIID-4453 > URL: https://issues.jboss.org/browse/TEIID-4453 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Kylin Soong > Fix For: 9.2 > > > The AuditEntity and database mapping needs to be updated to handle a semantic/string vdb version as well as potentially exposing more information from logoninfo events. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 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 resolved TEIID-4501. ----------------------------------- Resolution: Done Updated the resource adapter to default to the 34 url. > 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)

8 years, 2 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4502?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4502: ------------------------------------- I believe most quick start examples also have this in their VDBs. > 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)

8 years, 2 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4502?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4502. ----------------------------------- Resolution: Done removed in the quickstarts, embedded examples, source, and docs. > 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)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4503) Unhandled charset conversion exception in lobworkitem

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4503: ------------------------------------- Summary: Unhandled charset conversion exception in lobworkitem Key: TEIID-4503 URL: https://issues.jboss.org/browse/TEIID-4503 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.2 If getTextFiles is used on the File translator, the encoding is not validated so an exception can arise in the lobworkitem (or elsewhere) that is not handled gracefully. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[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)

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