July 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4996) Teiid embedded with Solr (exception max boolean clauses)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4996?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4996. ----------------------------------- Resolution: Done Added a default setting of 1024 to the translator. > Teiid embedded with Solr (exception max boolean clauses) > -------------------------------------------------------- > > Key: TEIID-4996 > URL: https://issues.jboss.org/browse/TEIID-4996 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Hend Amin > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.2 > > > I am using Teiid embedded with sorl. > i have a query like: > select field1 from solrCore where field2 in (v1,v2,v3 ..... v2000). > I get an expcetion > Caused by: org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024 > at org.apache.lucene.search.BooleanQuery$Builder.add(BooleanQuery.java:127) > at org.apache.lucene.search.BooleanQuery$Builder.add(BooleanQuery.java:117) > at org.apache.solr.parser.SolrQueryParserBase.getBooleanQuery(SolrQueryParserBase.java:514) > at org.apache.solr.parser.SolrQueryParserBase.getBooleanQuery(SolrQueryParserBase.java:490) > > If i am querying solr directly, i can work around the restriction of 1024 Boolean queries by using > field2:(v1 v2 v3 ... v1000) OR field2:(v1001 v1002 v1003 ... v2000) but with Teiid i can not do this and i get the exception. > > if i split the query field2 in (v1,v2,v3 ..... v1000) OR field2 in (v1001,v1002,v1003 ..... v2000) teiid groups this in one statement. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4996) Teiid embedded with Solr (exception max boolean clauses)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4996?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4996: ---------------------------------- Component/s: Misc. Connectors Fix Version/s: 10.0 9.3.2 Workaround Description: The workaround for older releases is to set the translator override property maxInCriteriaSize to 1024. Workaround: Workaround Exists > Teiid embedded with Solr (exception max boolean clauses) > -------------------------------------------------------- > > Key: TEIID-4996 > URL: https://issues.jboss.org/browse/TEIID-4996 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Hend Amin > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.2 > > > I am using Teiid embedded with sorl. > i have a query like: > select field1 from solrCore where field2 in (v1,v2,v3 ..... v2000). > I get an expcetion > Caused by: org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024 > at org.apache.lucene.search.BooleanQuery$Builder.add(BooleanQuery.java:127) > at org.apache.lucene.search.BooleanQuery$Builder.add(BooleanQuery.java:117) > at org.apache.solr.parser.SolrQueryParserBase.getBooleanQuery(SolrQueryParserBase.java:514) > at org.apache.solr.parser.SolrQueryParserBase.getBooleanQuery(SolrQueryParserBase.java:490) > > If i am querying solr directly, i can work around the restriction of 1024 Boolean queries by using > field2:(v1 v2 v3 ... v1000) OR field2:(v1001 v1002 v1003 ... v2000) but with Teiid i can not do this and i get the exception. > > if i split the query field2 in (v1,v2,v3 ..... v1000) OR field2 in (v1001,v1002,v1003 ..... v2000) teiid groups this in one statement. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4995) Investigate use of org.apache.poi.ss.usermodel.DataFormatter in Excel translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4995?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4995: --------------------------------------- There needs to be some additional considerations here. The current functionality is consistent with the data model. Making the functionality consistent with the formatting can be more challenging. If we're not just targeting default formatting, then there's a potential that the actual sheet formatting changes for arbitrary cell ranges, which would be hard to capture in the metadata. Can we clarify how we expect to capture the formatting details - a single execution flag "useDefaultFormatting", at import (at a column level or down to cell ranges), etc.? > Investigate use of org.apache.poi.ss.usermodel.DataFormatter in Excel translator > -------------------------------------------------------------------------------- > > Key: TEIID-4995 > URL: https://issues.jboss.org/browse/TEIID-4995 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.12.6_2, 8.12.11.6_3, 9.2.4 > Environment: Excel translator > Integer values in string columns > Reporter: Marc Shirley > Assignee: Steven Hawkins > > For integer values in a string column, values are displayed as a decimal value (for example, a value "5" is displayed as "5.0"). It looks like org.apache.poi.ss.usermodel.DataFormatter [1] by default attempts to format values in the same manner as Excel would display it [2], and would result in the integer value "5" being displayed as "5". In the case of string columns, this would avoid the user needing to modify source data to compensate as indicated as workarounds in TEIID-3947. > [1] https://poi.apache.org/apidocs/org/apache/poi/ss/usermodel/DataFormatter.... > [2] The default number format will mimic the Excel General format: "#" for whole numbers and "#.##########" for decimal numbers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4996) Teiid embedded with Solr (exception max boolean clauses)

by Hend Amin (JIRA)

Hend Amin created TEIID-4996: -------------------------------- Summary: Teiid embedded with Solr (exception max boolean clauses) Key: TEIID-4996 URL: https://issues.jboss.org/browse/TEIID-4996 Project: Teiid Issue Type: Bug Reporter: Hend Amin Assignee: Steven Hawkins I am using Teiid embedded with sorl. i have a query like: select field1 from solrCore where field2 in (v1,v2,v3 ..... v2000). I get an expcetion Caused by: org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024 at org.apache.lucene.search.BooleanQuery$Builder.add(BooleanQuery.java:127) at org.apache.lucene.search.BooleanQuery$Builder.add(BooleanQuery.java:117) at org.apache.solr.parser.SolrQueryParserBase.getBooleanQuery(SolrQueryParserBase.java:514) at org.apache.solr.parser.SolrQueryParserBase.getBooleanQuery(SolrQueryParserBase.java:490) If i am querying solr directly, i can work around the restriction of 1024 Boolean queries by using field2:(v1 v2 v3 ... v1000) OR field2:(v1001 v1002 v1003 ... v2000) but with Teiid i can not do this and i get the exception. if i split the query field2 in (v1,v2,v3 ..... v1000) OR field2 in (v1001,v1002,v1003 ..... v2000) teiid groups this in one statement. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4993) for each row trigger forcing txn to start

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4993?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4993. ----------------------------------- Resolution: Done Updated the logic to allow for each row procedures to be more selective in starting a transaction - other than scenarios requiring a transaction always, we'll only start a txn if multiple rows are modified when auto commit txn is off. The detection was also narrowed and corrected for RelationalPlan in general. > for each row trigger forcing txn to start > ----------------------------------------- > > Key: TEIID-4993 > URL: https://issues.jboss.org/browse/TEIID-4993 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.2 > > > TEIID-4504 relaxed when atomic blocks started transactions, but it did not address for each row procedure plans. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4926) Couchbase - unable to retrieve data if using 'convert' in view definition

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4926?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4926: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1455927|https://bugzilla.redhat.com/show_bug.cgi?id=1455927] from ON_QA to VERIFIED > Couchbase - unable to retrieve data if using 'convert' in view definition > ------------------------------------------------------------------------- > > Key: TEIID-4926 > URL: https://issues.jboss.org/browse/TEIID-4926 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.3, 8.12.x-6.4 > Reporter: Juraj Duráni > Assignee: Kylin Soong > Priority: Blocker > Fix For: 9.3, 8.12.x-6.4 > > > I have a simple document structure in Couchbase (no nested documents, all values are strings, integers, and booleans). > I have a source model with proper types (strings, integers, booleans) and view model defined with my target types (float, double, date,...) all with appropriate conversion. > There are basically two issues: > - When I try to retrieve all data from the view, Teiid ends with exception \[1\]. This is wired. > - When I try to use explicit convert on some columns from source table (not view) it ends with similar exception \[2\]. > Additional information: > I represent 'Null' values by excluding key from the document (nevertheless, same error occurs even if I add explicit "key":null to the definition of the document). > \[1\] > TEIID10076 Invalid conversion from type class java.lang.Integer with value '-24' to type class java.sql.Date > \[2\] - case for data value > TEIID10076 Invalid conversion from type class java.lang.Object with value '\{\}' to type class java.sql.Date > \[3\] - Queries > {code:sql} > OK - select * from couchbase.smalla > FAIL - select * from bqt1.smalla > FAIL - select convert(datevalue, date) from couchbase.smalla > {code} > \[4\] VDB definition > {code:sql} > -- source model > SET NAMESPACE 'http://www.teiid.org/translator/couchbase/2017' AS teiid_couchbase; > CREATE FOREIGN TABLE SmallA ( > documentID string, > FloatNum integer OPTIONS (NAMEINSOURCE '`smalla`.`FloatNum`'), > IntKey integer PRIMARY KEY OPTIONS (NAMEINSOURCE '`smalla`.`IntKey`'), > BigIntegerValue integer OPTIONS (NAMEINSOURCE '`smalla`.`BigIntegerValue`'), > StringKey string OPTIONS (NAMEINSOURCE '`smalla`.`StringKey`'), > CharValue string OPTIONS (NAMEINSOURCE '`smalla`.`CharValue`'), > LongNum integer OPTIONS (NAMEINSOURCE '`smalla`.`LongNum`'), > type string OPTIONS (NAMEINSOURCE '`smalla`.`type`'), > DoubleNum integer OPTIONS (NAMEINSOURCE '`smalla`.`DoubleNum`'), > ObjectValue string OPTIONS (NAMEINSOURCE '`smalla`.`ObjectValue`'), > ShortValue integer OPTIONS (NAMEINSOURCE '`smalla`.`ShortValue`'), > BigDecimalValue integer OPTIONS (NAMEINSOURCE '`smalla`.`BigDecimalValue`'), > DateValue string OPTIONS (NAMEINSOURCE '`smalla`.`DateValue`'), > BooleanValue boolean OPTIONS (NAMEINSOURCE '`smalla`.`BooleanValue`'), > TimestampValue string OPTIONS (NAMEINSOURCE '`smalla`.`TimestampValue`'), > ByteNum integer OPTIONS (NAMEINSOURCE '`smalla`.`ByteNum`'), > StringNum string OPTIONS (NAMEINSOURCE '`smalla`.`StringNum`'), > TimeValue string OPTIONS (NAMEINSOURCE '`smalla`.`TimeValue`'), > IntNum integer OPTIONS (NAMEINSOURCE '`smalla`.`IntNum`') > ) OPTIONS (NAMEINSOURCE '`smalla`', UPDATABLE FALSE, "teiid_couchbase:ISARRAYTABLE" 'false', "teiid_couchbase:NAMEDTYPEPAIR" '`type`:''SmallA'''); > -- view model > CREATE VIEW SmallA ( > IntKey integer PRIMARY KEY, > StringKey string, > IntNum integer, > StringNum string, > FloatNum float, > LongNum long, > DoubleNum double, > ByteNum byte, > DateValue date, > TimeValue time, > TimestampValue timestamp, > BooleanValue boolean, > CharValue char(1), > ShortValue short, > BigIntegerValue biginteger, > BigDecimalValue bigdecimal, > ObjectValue object) > AS > SELECT > IntKey, StringKey, IntNum, StringNum, convert(FloatNum, float) AS FloatNum, convert(LongNum, long) AS LongNum, > convert(DoubleNum, double) AS DoubleNum, convert(ByteNum, byte) AS ByteNum, convert(DateValue, date) AS DateValue, > convert(TimeValue, time) AS TimeValue, convert(TimestampValue, timestamp) AS TimstampValue, BooleanValue, > convert(CharValue, char) AS CharValue, convert(ShortValue, short) AS ShortValue, convert(BigIntegerValue, biginteger) AS BigIntegerValue, > convert(BigDecimalValue, bigdecimal) AS BigDecimalValue, convert(ObjectValue, object) AS ObjectValue > FROM > Couchbase.SmallA; > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4995) Investigate use of org.apache.poi.ss.usermodel.DataFormatter in Excel translator

by Marc Shirley (JIRA)

Marc Shirley created TEIID-4995: ----------------------------------- Summary: Investigate use of org.apache.poi.ss.usermodel.DataFormatter in Excel translator Key: TEIID-4995 URL: https://issues.jboss.org/browse/TEIID-4995 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 9.2.4, 8.12.11.6_3, 8.7.12.6_2 Environment: Excel translator Integer values in string columns Reporter: Marc Shirley Assignee: Steven Hawkins For integer values in a string column, values are displayed as a decimal value (for example, a value "5" is displayed as "5.0"). It looks like org.apache.poi.ss.usermodel.DataFormatter [1] by default attempts to format values in the same manner as Excel would display it [2], and would result in the integer value "5" being displayed as "5". In the case of string columns, this would avoid the user needing to modify source data to compensate as indicated as workarounds in TEIID-3947. [1] https://poi.apache.org/apidocs/org/apache/poi/ss/usermodel/DataFormatter.... [2] The default number format will mimic the Excel General format: "#" for whole numbers and "#.##########" for decimal numbers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4994) For materialization, use "Ignore return values" option to improve performance

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4994?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4994: ------------------------------- Affects Version/s: 9.3.2 > For materialization, use "Ignore return values" option to improve performance > ----------------------------------------------------------------------------- > > Key: TEIID-4994 > URL: https://issues.jboss.org/browse/TEIID-4994 > Project: Teiid > Issue Type: Enhancement > Components: Infinispan > Affects Versions: 8.12.x-6.4, 9.3.2 > Reporter: Van Halbert > Assignee: Ramesh Reddy > > For a performance improvement, change to use Flag.IGNORE_RETURN_VALUES > Cache noPreviousValueCache = cache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES); > noPreviousValueCache.put(k, v); > or can use ConfigurationBuilder settings: > ConfigurationBuilder cb = new ConfigurationBuilder(); > cb.unsafe().unreliableReturnValues(true); -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4994) For materialization, use "Ignore return values" option to improve performance

by Van Halbert (JIRA)

Van Halbert created TEIID-4994: ---------------------------------- Summary: For materialization, use "Ignore return values" option to improve performance Key: TEIID-4994 URL: https://issues.jboss.org/browse/TEIID-4994 Project: Teiid Issue Type: Enhancement Components: Infinispan Affects Versions: 8.12.x-6.4 Reporter: Van Halbert Assignee: Ramesh Reddy For a performance improvement, change to use Flag.IGNORE_RETURN_VALUES Cache noPreviousValueCache = cache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES); noPreviousValueCache.put(k, v); or can use ConfigurationBuilder settings: ConfigurationBuilder cb = new ConfigurationBuilder(); cb.unsafe().unreliableReturnValues(true); -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4993) for each row trigger forcing txn to start

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4993?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4993: ---------------------------------- Description: TEIID-4504 relaxed when atomic blocks started transactions, but it did not address for each row procedure plans. (was: TEIID-4505 relaxed when atomic blocks started transactions, but it did not address for each row procedure plans.) > for each row trigger forcing txn to start > ----------------------------------------- > > Key: TEIID-4993 > URL: https://issues.jboss.org/browse/TEIID-4993 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.2 > > > TEIID-4504 relaxed when atomic blocks started transactions, but it did not address for each row procedure plans. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 July 2017