September 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5085) NullPointerException after SortUtility blocks in initialSort

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5085: ------------------------------------- Summary: NullPointerException after SortUtility blocks in initialSort Key: TEIID-5085 URL: https://issues.jboss.org/browse/TEIID-5085 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.0 If SortUtility blocks during the initial sort, an npe is later thrown as can be seen in TestJDBCSocketTransport.testXmlTableScrollable java.lang.NullPointerException at org.teiid.query.processor.relational.MergeJoinStrategy.compareToPrevious(MergeJoinStrategy.java:277) at org.teiid.query.processor.relational.MergeJoinStrategy.process(MergeJoinStrategy.java:235) at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:231) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:98) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) at org.teiid.query.processor.BatchCollector$BatchProducerTupleSource.nextTuple(BatchCollector.java:90) at org.teiid.query.processor.relational.GroupingNode.groupPhase(GroupingNode.java:577) at org.teiid.query.processor.relational.GroupingNode.nextBatchDirect(GroupingNode.java:373) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:141) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:148) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:111) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:142) at org.teiid.query.processor.relational.SubqueryAwareEvaluator.evaluateSubquery(SubqueryAwareEvaluator.java:354) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 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 updated TEIID-4857: ---------------------------------- Fix Version/s: 8.12.x-6.4 > 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 > Affects Versions: 8.12.x-6.4 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.3, 8.12.x-6.4 > > > 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)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3494) TABLE() can execute in parallel

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3494?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3494: ------------------------------------- Fix Version/s: 10.x (was: 10.0) Assignee: (was: Steven Hawkins) Will consider this as part of the broader TEIID-4208. Effectively rewriting the existing nested table join logic will require plan cloning and a lot of other supporting logic. It's best to handle more general cases first. > TABLE() can execute in parallel > ------------------------------- > > Key: TEIID-3494 > URL: https://issues.jboss.org/browse/TEIID-3494 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Mark Addleman > Fix For: 10.x > > > it would be nice if the TABLE() construct was extended to support parallel source executions in the same way that joins can be executed in parallel. - See more at: https://developer.jboss.org/thread/259330#sthash.YjQyw4vR.dpuf -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5084) Executing query against a Flat File Source using new getTextFiles() procedure fails with *.vdb

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5084?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5084. ----------------------------------- Resolution: Rejected The TEIID-4857 change was not brought back yet. That will be added. > Executing query against a Flat File Source using new getTextFiles() procedure fails with *.vdb > ---------------------------------------------------------------------------------------------- > > Key: TEIID-5084 > URL: https://issues.jboss.org/browse/TEIID-5084 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.x-6.4 > Reporter: Barry LaFond > Assignee: Steven Hawkins > > TEIID-8457 changed the getTextFiles() procedure to return 5 columns in stead of 2. > Teiid Designer now generates 5 column result set in the Flat File importer. > Preview Data works correctly using the temp generated Dynamic VDB which does not include the *source* model. If you add that DDL back in the preview fails with: > 09:36:34,607 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue3) TEIID30020 Processing exception for request kbAwSo//6LsD.0 'TEIID30504 SourceModelForFlatFile: Inproper results returned. Expected 5 columns, but was 2'. Originally TeiidProcessingException ConnectorWorkItem.java:439. Enable more detailed logging to see the entire stacktrace. > When I create a *.vdb file and deploy, for this same Flat FIle view... Execute VDB fails with the same error. The *.vdb, of course, contains the source model. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5084) Executing query against a Flat File Source using new getTextFiles() procedure fails with *.vdb

by Barry LaFond (JIRA)

Barry LaFond created TEIID-5084: ----------------------------------- Summary: Executing query against a Flat File Source using new getTextFiles() procedure fails with *.vdb Key: TEIID-5084 URL: https://issues.jboss.org/browse/TEIID-5084 Project: Teiid Issue Type: Bug Affects Versions: 8.12.x-6.4 Reporter: Barry LaFond Assignee: Steven Hawkins TEIID-8457 changed the getTextFiles() procedure to return 5 columns in stead of 2. Teiid Designer now generates 5 column result set in the Flat File importer. Preview Data works correctly using the temp generated Dynamic VDB which does not include the *source* model. If you add that DDL back in the preview fails with: 09:36:34,607 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue3) TEIID30020 Processing exception for request kbAwSo//6LsD.0 'TEIID30504 SourceModelForFlatFile: Inproper results returned. Expected 5 columns, but was 2'. Originally TeiidProcessingException ConnectorWorkItem.java:439. Enable more detailed logging to see the entire stacktrace. When I create a *.vdb file and deploy, for this same Flat FIle view... Execute VDB fails with the same error. The *.vdb, of course, contains the source model. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5077) Couchbase strange behaviour for long numbers

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5077?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5077: ---------------------------------- Fix Version/s: 8.12.x-6.4 9.3.4 > Couchbase strange behaviour for long numbers > -------------------------------------------- > > Key: TEIID-5077 > URL: https://issues.jboss.org/browse/TEIID-5077 > Project: Teiid > Issue Type: Bug > Components: Documentation, Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Critical > Fix For: 10.0, 8.12.x-6.4, 9.3.4 > > > There is a strange limitation for storing large numbers (e.g. modelled as long) in Couchbase. > https://forums.couchbase.com/t/strange-behavior-when-saving-big-long-numb... > The same behaviour with value: 28341791043587382 > which is being stored and retreived as: 28341791043587384 > I feel we need to document this behaviour and provide hints how to overcome it. (Modelling of the column as string on Couchbase's side and defining a view). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5077) Couchbase strange behaviour for long numbers

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5077?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5077. ----------------------------------- Resolution: Done The resolution here is a new useDouble execution property that will inhibit pushdown of conversion to long, biginteger, bigdecimal and will import those types as double instead. > Couchbase strange behaviour for long numbers > -------------------------------------------- > > Key: TEIID-5077 > URL: https://issues.jboss.org/browse/TEIID-5077 > Project: Teiid > Issue Type: Bug > Components: Documentation, Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Critical > Fix For: 10.0 > > > There is a strange limitation for storing large numbers (e.g. modelled as long) in Couchbase. > https://forums.couchbase.com/t/strange-behavior-when-saving-big-long-numb... > The same behaviour with value: 28341791043587382 > which is being stored and retreived as: 28341791043587384 > I feel we need to document this behaviour and provide hints how to overcome it. (Modelling of the column as string on Couchbase's side and defining a view). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5077) Couchbase strange behaviour for long numbers

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5077?page=com.atlassian.jira.plugin... ] Work on TEIID-5077 started by Steven Hawkins. --------------------------------------------- > Couchbase strange behaviour for long numbers > -------------------------------------------- > > Key: TEIID-5077 > URL: https://issues.jboss.org/browse/TEIID-5077 > Project: Teiid > Issue Type: Bug > Components: Documentation, Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Critical > Fix For: 10.0 > > > There is a strange limitation for storing large numbers (e.g. modelled as long) in Couchbase. > https://forums.couchbase.com/t/strange-behavior-when-saving-big-long-numb... > The same behaviour with value: 28341791043587382 > which is being stored and retreived as: 28341791043587384 > I feel we need to document this behaviour and provide hints how to overcome it. (Modelling of the column as string on Couchbase's side and defining a view). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5043) Add an option to output plan text as yaml

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5043?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5043. ----------------------------------- Resolution: Done Changed the plan logging to be yaml. Did not yet change the user facing "show plan" text. > Add an option to output plan text as yaml > ----------------------------------------- > > Key: TEIID-5043 > URL: https://issues.jboss.org/browse/TEIID-5043 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > The plan text is close to yaml format. We should take a pass at converting it to yaml and making it more compact so that the plans displayed in the logs are more human readable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5073) Building Salesforce adapter/translator pair issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5073?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5073. ----------------------------------- Resolution: Done Added a new connectivity pair using the force 41 jars, but left the default as accessing the 40 api. The docs referring to building your own have been updated to removed that language. It seems that there are changes in nearly every revision that need to be accounted for. In this case additional dependencies were needed in the force 41 module. > Building Salesforce adapter/translator pair issues > -------------------------------------------------- > > Key: TEIID-5073 > URL: https://issues.jboss.org/browse/TEIID-5073 > Project: Teiid > Issue Type: Component Upgrade > Components: Salesforce Connector > Affects Versions: 9.2.3 > Environment: wildfly 10.0.0.Final and teiid-9.2.3 > Reporter: Thomas Esche > Assignee: Steven Hawkins > Labels: API, Salesforce > Fix For: 10.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > I tried to follow the instructions on https://github.com/teiid/salesforce to build a newer adapter/translator pair but I was not even able to build the provided v34 pair. > The "mvn clean install" produce the following error: > [INFO] ------------------------------------------------------------------------ > [INFO] Building Salesforce Resource Adapter API 34 1.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > Downloading: https://repository.jboss.org/nexus/content/repositories/thirdparty-upload... > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Salesforce API 34 .................................. SUCCESS [ 1.091 s] > [INFO] Salesforce Translator 34 ........................... SUCCESS [ 2.105 s] > [INFO] Salesforce Resource Adapter API 34 ................. FAILURE [ 1.596 s] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 5.490 s > [INFO] Finished at: 2017-09-20T11:13:59+02:00 > [INFO] Final Memory: 35M/425M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project connector-salesforce-34: Could not resolve dependencies for project org.jboss.teiid.connectors.salesforce-34:connector-salesforce-34:jar:1.0-SNAPSHOT: Could not find artifact org.jboss.teiid.connectors:connector-salesforce:rar:9.0.0.Final in thirdparty-uploads (https://repository.jboss.org/nexus/content/repositories/thirdparty-uploads/) -> [Help 1] > After removing the dependencies block in the ...\connector-salesforce-34\pom.xml maven works, but it seems to create an invalid adapter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2017