October 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4487) NPE if using multi-value prepared INSERT

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4487?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4487: ---------------------------------- Component/s: Query Engine > NPE if using multi-value prepared INSERT > ---------------------------------------- > > Key: TEIID-4487 > URL: https://issues.jboss.org/browse/TEIID-4487 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 9.1 > > > If user issues multi-value insert, Teiid throws NPE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4487) NPE if using multi-value prepared INSERT

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4487?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4487: ---------------------------------- Component/s: (was: Salesforce Connector) Fix Version/s: 9.1 Summary: NPE if using multi-value prepared INSERT (was: Salesfroce - NPE if using multi-value INSERT) Affects Version/s: 8.7 (was: 8.12.5) > NPE if using multi-value prepared INSERT > ---------------------------------------- > > Key: TEIID-4487 > URL: https://issues.jboss.org/browse/TEIID-4487 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 9.1 > > > If user issues multi-value insert, Teiid throws NPE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4487) Salesfroce - NPE if using multi-value INSERT

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4487?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4487: --------------------------------------- It is not the proper way, but it should still work. The issue is that for multiple values our under the covers handling is to use a union all query, which doesn't handle the resolving well. > Salesfroce - NPE if using multi-value INSERT > -------------------------------------------- > > Key: TEIID-4487 > URL: https://issues.jboss.org/browse/TEIID-4487 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If user issues multi-value insert, Teiid throws NPE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4487) Salesfroce - NPE if using multi-value INSERT

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4487?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4487: ------------------------------------- I do not think the above is correct way to call the prepared statement, see this for example http://stackoverflow.com/questions/4355046/java-insert-multiple-rows-into... > Salesfroce - NPE if using multi-value INSERT > -------------------------------------------- > > Key: TEIID-4487 > URL: https://issues.jboss.org/browse/TEIID-4487 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If user issues multi-value insert, Teiid throws NPE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4487) Salesfroce - NPE if using multi-value INSERT

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4487?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4487: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1381229 Bugzilla Update: Perform > Salesfroce - NPE if using multi-value INSERT > -------------------------------------------- > > Key: TEIID-4487 > URL: https://issues.jboss.org/browse/TEIID-4487 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If user issues multi-value insert, Teiid throws NPE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4485) import-vdb VDB name case-sensitive

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4485?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4485. ----------------------------------- Resolution: Done Changing service names to not be case sensitive > import-vdb VDB name case-sensitive > ---------------------------------- > > Key: TEIID-4485 > URL: https://issues.jboss.org/browse/TEIID-4485 > Project: Teiid > Issue Type: Bug > Components: VDB > Affects Versions: 8.7 > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.5 > > > I have built couple of VDBs using designer, their names are all CAPS and wanted to import these 2 VDBs as views in my 3rd VDB. As the VDB name is cases insensitive in connect string i used lower case to connect to the VDB to do JDBC import. After i completed my 3rd VDB when i tried to deploy the VDB onto the server it is going into INACTIVE state, after changing my connection string to upper case and reimporting the VDB i was able to deploy the 3rd VDB and it state turned to ACTIVE. > The VDB import definition seem's to be case sensitive and this may be the cause of the errors. > I haven't tested this in Dynamic VDB. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4488) Add a more localized way to set the default escape

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4488?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4488. ----------------------------------- Resolution: Done added and documented using the session variable backslashMatchDefaultEscape > Add a more localized way to set the default escape > -------------------------------------------------- > > Key: TEIID-4488 > URL: https://issues.jboss.org/browse/TEIID-4488 > Project: Teiid > Issue Type: Quality Risk > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > To support geoserver and ODBC integration in general we should provide a more localized way of setting the default escape for like predicates. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4357) Add documentation on exposing Teiid as a GeoServer data source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4357?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4357. ----------------------------------- Resolution: Done Added the basic integration steps to the client dev guide covering any Teiid specific nuances. Also added TEIID-4488 so that the backslash handling could be localized. > Add documentation on exposing Teiid as a GeoServer data source > -------------------------------------------------------------- > > Key: TEIID-4357 > URL: https://issues.jboss.org/browse/TEIID-4357 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.1 > > > Based on the details in TEIID-3869, need to document how Teiid can be exposed as a GeoServer data source -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 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 Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4489?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4489: ------------------------------------ And it needs to be checked that, if the defaults are selected and 10 to 20 data sources are selected, it recommends the MEDIUM size, and then the LARGE is recommended when 21 or above is selected. > 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, 3 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 Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4489?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4489: ------------------------------------ I say clear, because I'm not sure if whats stated: 16 cores, with at least 32 GB RAM. 2 DV instances. (small means may be 5 ~10 sources, rows into millions, YMMV) means each instance to be 16 cores/32GB or split it to be 8 cores/16GB per instance.. > 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 > Priority: Minor > > 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, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2016