May 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4910) Update build to utilize a maven docker plugin

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4910?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4910: ---------------------------------- Description: We need to automate creating and pushing the docker image. (was: We need to automate creating and pushing the docker image. It also needs updated to use java 8.) Fix Version/s: 10.0 (was: 9.3) > Update build to utilize a maven docker plugin > --------------------------------------------- > > Key: TEIID-4910 > URL: https://issues.jboss.org/browse/TEIID-4910 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > We need to automate creating and pushing the docker image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4918) Enhance infinispan 7.1 support for muti-threaded puts or using putAll

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4918?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4918: ------------------------------------- Yes, Bulk Update support is what is needed here. We can not really use PutAll, as Complex Objects (children objects) will not be handled correctly. We would really need to write a server-side function and use that. Bulk Insert on top level objects is the only scenario that simple to achieve with PutAll. The next issue is doing these operations atomically which I do not think I have a good thought process yet. > Enhance infinispan 7.1 support for muti-threaded puts or using putAll > --------------------------------------------------------------------- > > Key: TEIID-4918 > URL: https://issues.jboss.org/browse/TEIID-4918 > Project: Teiid > Issue Type: Enhancement > Components: Infinispan > Affects Versions: 9.3 > Reporter: Van Halbert > Assignee: Ramesh Reddy > > For performance reasons, it was requested that the infinispan connector/translator be enhanced to be multi-threaded when doing batch inserts or try using the putAll option. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

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

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4926: ----------------------------------- Summary: 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 Reporter: Juraj Duráni Assignee: Steven Hawkins Priority: Blocker 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)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4875) Planning issue with multiple aggregate decompositions through a join tree

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4875?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4875: --------------------------------------- TEIID-4861 is required as well for both 6.3 and 6.4. > Planning issue with multiple aggregate decompositions through a join tree > ------------------------------------------------------------------------- > > Key: TEIID-4875 > URL: https://issues.jboss.org/browse/TEIID-4875 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3, 8.12.x-6.4, 9.2.3, 8.12.11.6_3 > > > The logic for determining other symbols from aggregates will not work correctly when a staged grouping is initially pushed and another staged grouping is then pushed above a join that is above that location (typically due to join predicates that pull in other groups). > A query such as: > SELECT max(t3.e4), max(t2.e4) as s FROM pm1.g1 as t1, pm1.g2 as t2, pm1.g3 as t3, pm1.g4 as t4, pm2.g1 as t5 WHERE t1.e1 = t2.e1 and (t2.e2 = t3.e2 and t1.e3 || t2.e3 = t3.e3) and t3.e3 = t4.e3 and t4.e4 = t5.e4 > With capabilities that disable join pushdown will fail with an assertionerror that a staged grouping symbol cannot be found during the initialization of the parent join node. > java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null > at org.teiid.core.util.Assertion.failed(Assertion.java:73) > at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100) > at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92) > at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:367) > at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:133) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:96) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102) > at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:91) > at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:226) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4924) Prepare to push teiis-spring-boot to maven central

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4924?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4924: --------------------------------------- Try contacting jboss.org for greater nexus rights. > Prepare to push teiis-spring-boot to maven central > -------------------------------------------------- > > Key: TEIID-4924 > URL: https://issues.jboss.org/browse/TEIID-4924 > Project: Teiid > Issue Type: Sub-task > Reporter: Kylin Soong > Assignee: Steven Hawkins > Fix For: 10.0 > > > Prepare to push teiis-spring-boot to maven central. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4901) Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4901?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4901: ------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1452743, https://bugzilla.redhat.com/show_bug.cgi?id=1450489 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1452743) > Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-4901 > URL: https://issues.jboss.org/browse/TEIID-4901 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.12.10.6_3 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.3, 8.12.x-6.4, 8.12.11.6_3 > > > Add the capability to split an independent accessnode into multiple parallel source queries when the number of IN criteria values exceed the translator's MaxInCriteriaSize value. This would be similar handling to what we perform on the dependent side of a dependent join when the number of values exceed the size. > The background for this request is regarding input to an SAP gateway source which has a MaxInCriteriaSize of 3 due to URL length restrictions. Currently, if 4 values are submitted the full result set is returned to be processed within the Teiid engine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4925) Importing a non-existing VDB gives no warning

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4925?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4925: --------------------------------------- We should add an INFO log, but the intent is to wait for that imported VDB to become available - even if it is not yet deployed. > Importing a non-existing VDB gives no warning > --------------------------------------------- > > Key: TEIID-4925 > URL: https://issues.jboss.org/browse/TEIID-4925 > Project: Teiid > Issue Type: Enhancement > Environment: * Wildfly 10 > * Teiid Server 9.2.3 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Fix For: 9.2.3 > > Attachments: ReferenceData.png > > > When importing a "non-existing VDB" in a VDB, when the VDB is deployed, the VDB status is LOADING, and nothing else happens. > Ideally a warning should be thrown in logs. > Ex: > <code> > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <vdb name="ReferenceDataVDB" version="1"> > <description>ReferenceData VDB</description> > <import-vdb name="NonExistingVDB" version="1"/> > > <model name="ReferenceData" type="VIRTUAL"> > ..... > </code> > Logs: > <panel> > 12:56:11,529 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "ReferenceData-vdb.xml" (runtime-name: "ReferenceData-vdb.xml") > 12:56:11,953 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "ReferenceData-vdb.xml" (runtime-name : "ReferenceData-vdb.xml") > </panel> -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4857) Add file metadata such as creation and last modified date to file translator functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4857?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4857: --------------------------------------- > In the event that someone is using and relying on * to resolve only 2 columns from this procedure, it will now return 5 columns. I added a backwards compatibility check in another commit that mitigates this concern. Only if someone is using embedded, such that the metadata is reimported, and relying on * would there be an issue. But that does also bring up that for backporting a corresponding Teiid Designer issue will need to be created to update the file importer logic that exposes the file procedures. Otherwise the teiid connection importer will need to be used. > Add file metadata such as creation and last modified date to file translator functions > -------------------------------------------------------------------------------------- > > Key: TEIID-4857 > URL: https://issues.jboss.org/browse/TEIID-4857 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.3 > > > Add file metadata such as creation date and last modified date to the data returned by the file translator functions (getFiles/getTextFiles). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4925) Importing a non-existing VDB gives no warning

by Pedro Inácio (JIRA)

Pedro Inácio created TEIID-4925: ----------------------------------- Summary: Importing a non-existing VDB gives no warning Key: TEIID-4925 URL: https://issues.jboss.org/browse/TEIID-4925 Project: Teiid Issue Type: Enhancement Environment: * Wildfly 10 * Teiid Server 9.2.3 Reporter: Pedro Inácio Assignee: Steven Hawkins Fix For: 9.2.3 Attachments: ReferenceData.png When importing a "non-existing VDB" in a VDB, when the VDB is deployed, the VDB status is LOADING, and nothing else happens. Ideally a warning should be thrown in logs. Ex: <code> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <vdb name="ReferenceDataVDB" version="1"> <description>ReferenceData VDB</description> <import-vdb name="NonExistingVDB" version="1"/> <model name="ReferenceData" type="VIRTUAL"> ..... </code> Logs: <panel> 12:56:11,529 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "ReferenceData-vdb.xml" (runtime-name: "ReferenceData-vdb.xml") 12:56:11,953 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "ReferenceData-vdb.xml" (runtime-name : "ReferenceData-vdb.xml") </panel> -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4875) Planning issue with multiple aggregate decompositions through a join tree

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4875?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4875: --------------------------------------- More than likely it is not this issue that needs reopened, unless you see something similar on master. I'll have to examine the backport and see what is going on and if there are other issues that are applicable. > Planning issue with multiple aggregate decompositions through a join tree > ------------------------------------------------------------------------- > > Key: TEIID-4875 > URL: https://issues.jboss.org/browse/TEIID-4875 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3, 8.12.x-6.4, 9.2.3, 8.12.11.6_3 > > > The logic for determining other symbols from aggregates will not work correctly when a staged grouping is initially pushed and another staged grouping is then pushed above a join that is above that location (typically due to join predicates that pull in other groups). > A query such as: > SELECT max(t3.e4), max(t2.e4) as s FROM pm1.g1 as t1, pm1.g2 as t2, pm1.g3 as t3, pm1.g4 as t4, pm2.g1 as t5 WHERE t1.e1 = t2.e1 and (t2.e2 = t3.e2 and t1.e3 || t2.e3 = t3.e3) and t3.e3 = t4.e3 and t4.e4 = t5.e4 > With capabilities that disable join pushdown will fail with an assertionerror that a staged grouping symbol cannot be found during the initialization of the parent join node. > java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null > at org.teiid.core.util.Assertion.failed(Assertion.java:73) > at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100) > at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92) > at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:367) > at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:133) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:96) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102) > at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:91) > at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:226) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2017