July 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4311) Teiid Admin Api not support to create XA datasource on Jboss server.

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4311?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-4311: ----------------------------------- Assignee: Ramesh Reddy (was: Kylin Soong) > Teiid Admin Api not support to create XA datasource on Jboss server. > -------------------------------------------------------------------- > > Key: TEIID-4311 > URL: https://issues.jboss.org/browse/TEIID-4311 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.13.x > Reporter: Prakash Jape > Assignee: Ramesh Reddy > Fix For: 9.1, 9.0.2 > > > Teiid Admin api does not support or does not have capability to create XA datasource on Jboss server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4289) Add transaction command support for syntax BEGIN/ROLLBACK/COMMIT WORK

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4289?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4289: --------------------------------- Fix Version/s: 8.7.8.6_2 > Add transaction command support for syntax BEGIN/ROLLBACK/COMMIT WORK > --------------------------------------------------------------------- > > Key: TEIID-4289 > URL: https://issues.jboss.org/browse/TEIID-4289 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.7.6.6_2 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.8.6_2 > > > This request appears to be an expansion of TEIID-1701 to add syntax like the below as an alias for transactional commands. This would be in line to make commands portable from other vendor DBs such as PostgreSQL/SQL Server/DB2/MySQL. > BEGIN WORK > ROLLBACK WORK > COMMIT WORK -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3889) asynch start transaction / rollback throws exception

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3889?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-3889. -------------------------------- Resolution: Done > asynch start transaction / rollback throws exception > ---------------------------------------------------- > > Key: TEIID-3889 > URL: https://issues.jboss.org/browse/TEIID-3889 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.8.6_2, 8.12.4, 8.13 > > > If a local transaction is requested, but no statements are issued to start it, then a asynch rollback will go to the server side and throw an exception rather than simply toggling the autocommit flag. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3889) asynch start transaction / rollback throws exception

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3889?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3889: ---------------------------------- > asynch start transaction / rollback throws exception > ---------------------------------------------------- > > Key: TEIID-3889 > URL: https://issues.jboss.org/browse/TEIID-3889 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.4 > > > If a local transaction is requested, but no statements are issued to start it, then a asynch rollback will go to the server side and throw an exception rather than simply toggling the autocommit flag. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3889) asynch start transaction / rollback throws exception

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3889?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3889: --------------------------------- Fix Version/s: 8.7.8.6_2 > asynch start transaction / rollback throws exception > ---------------------------------------------------- > > Key: TEIID-3889 > URL: https://issues.jboss.org/browse/TEIID-3889 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.4, 8.7.8.6_2 > > > If a local transaction is requested, but no statements are issued to start it, then a asynch rollback will go to the server side and throw an exception rather than simply toggling the autocommit flag. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4320) Costing calculation issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4320?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4320: ---------------------------------- > Costing calculation issues > -------------------------- > > Key: TEIID-4320 > URL: https://issues.jboss.org/browse/TEIID-4320 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.1, 8.13.6, 9.0.1 > > > When determining if a dependent join should be used we'll rule out too many scenarios based upon requiring additional ndv info - when that can be determined from cardinality alone. Also we are inappropriately assuming key usage in predicate costing - as it does not consider the node which may not represent a single table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4320) Costing calculation issues

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4320: ------------------------------------- Summary: Costing calculation issues Key: TEIID-4320 URL: https://issues.jboss.org/browse/TEIID-4320 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 9.1, 8.13.6, 9.0.1 When determining if a dependent join should be used we'll rule out too many scenarios based upon requiring additional ndv info - when that can be determined from cardinality alone. Also we are inappropriately assuming key usage in predicate costing - as it does not consider the node which may not represent a single table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4303) Insert into temporary table fails

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4303?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4303. ----------------------------------- Resolution: Rejected > Insert into temporary table fails > --------------------------------- > > Key: TEIID-4303 > URL: https://issues.jboss.org/browse/TEIID-4303 > Project: Teiid > Issue Type: Bug > Affects Versions: 9.0 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: debugplan.txt > > > When executing a insert query in a temporary table the execution fails with the following error: > 2016-06-28 08:54:35,700 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Closed execution > 2016-06-28 08:54:35,700 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Closed connection > 2016-06-28 08:54:35,700 DEBUG [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 END SRC COMMAND: endTime=2016-06-28 08:54:35.7 requestID=3bZw8VxEr4t7.26 sourceCommandID=4 executionID=30 txID=TransactionImple < ac, BasicAction: 0:ffff7f000101:2f4a8c3a:576d4165:72fc status: ActionStatus.ABORTED > modelName=iziswh translatorName=sybase sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security finalRowCount=21504 cpuTime(ns)=120503397 > 2016-06-28 08:54:35,701 INFO [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 ERROR USER COMMAND: endTime=2016-06-28 08:54:35.701 requestID=3bZw8VxEr4t7.26 txID=TransactionImple < ac, BasicAction: 0:ffff7f000101:2f4a8c3a:576d4165:72fc status: ActionStatus.ABORTED > sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security vdbName=vdb3 vdbVersion=14 finalRowCount=null > 2016-06-28 08:54:35,701 WARN [org.teiid.PROCESSOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 TEIID30020 Processing exception for request 3bZw8VxEr4t7.26 'TEIID30223 javax.transaction.RollbackException: ARJUNA016083: Can't register synchronization because the transaction is in aborted state'. Originally TeiidProcessingException TransactionImple.java:396. Enable more detailed logging to see the entire stacktrace. > 2016-06-28 08:54:35,701 WARN [com.arjuna.ats.arjuna] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 ARJUNA012077: Abort called on already aborted atomic action 0:ffff7f000101:2f4a8c3a:576d4165:72fc > 2016-06-28 08:54:35,702 INFO [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 END USER COMMAND: endTime=2016-06-28 08:54:35.702 requestID=3bZw8VxEr4t7.26 txID=null sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security vdbName=vdb3 vdbVersion=14 finalRowCount=0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4303) Insert into temporary table fails

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIID-4303?page=com.atlassian.jira.plugin... ] Bram Gadeyne commented on TEIID-4303: ------------------------------------- Extending the default timeout solved the problem. > Insert into temporary table fails > --------------------------------- > > Key: TEIID-4303 > URL: https://issues.jboss.org/browse/TEIID-4303 > Project: Teiid > Issue Type: Bug > Affects Versions: 9.0 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: debugplan.txt > > > When executing a insert query in a temporary table the execution fails with the following error: > 2016-06-28 08:54:35,700 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Closed execution > 2016-06-28 08:54:35,700 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Closed connection > 2016-06-28 08:54:35,700 DEBUG [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 END SRC COMMAND: endTime=2016-06-28 08:54:35.7 requestID=3bZw8VxEr4t7.26 sourceCommandID=4 executionID=30 txID=TransactionImple < ac, BasicAction: 0:ffff7f000101:2f4a8c3a:576d4165:72fc status: ActionStatus.ABORTED > modelName=iziswh translatorName=sybase sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security finalRowCount=21504 cpuTime(ns)=120503397 > 2016-06-28 08:54:35,701 INFO [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 ERROR USER COMMAND: endTime=2016-06-28 08:54:35.701 requestID=3bZw8VxEr4t7.26 txID=TransactionImple < ac, BasicAction: 0:ffff7f000101:2f4a8c3a:576d4165:72fc status: ActionStatus.ABORTED > sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security vdbName=vdb3 vdbVersion=14 finalRowCount=null > 2016-06-28 08:54:35,701 WARN [org.teiid.PROCESSOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 TEIID30020 Processing exception for request 3bZw8VxEr4t7.26 'TEIID30223 javax.transaction.RollbackException: ARJUNA016083: Can't register synchronization because the transaction is in aborted state'. Originally TeiidProcessingException TransactionImple.java:396. Enable more detailed logging to see the entire stacktrace. > 2016-06-28 08:54:35,701 WARN [com.arjuna.ats.arjuna] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 ARJUNA012077: Abort called on already aborted atomic action 0:ffff7f000101:2f4a8c3a:576d4165:72fc > 2016-06-28 08:54:35,702 INFO [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 END USER COMMAND: endTime=2016-06-28 08:54:35.702 requestID=3bZw8VxEr4t7.26 txID=null sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security vdbName=vdb3 vdbVersion=14 finalRowCount=0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4269) numeric calculated fields not displayed with odata4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4269?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4269: --------------------------------------- > What I was saying is "convert" function ignores the precision and scale values if they are mentioned on query. That is correct. The type system if very loose around the base java types (String, Double, etc.) such that constraints are largely ignored. > The solution could be ignoring the metadata provided and make odata layer metadata as wide as possible, but seems wrong. For the old xml production logic at times we consulted the metadata at the edge to modify results. We could do something like that here - that would be easier than making the engine aware as the type system through out is just based upon the Class. > numeric calculated fields not displayed with odata4 > --------------------------------------------------- > > Key: TEIID-4269 > URL: https://issues.jboss.org/browse/TEIID-4269 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.13.3 > Reporter: Mirco Marchitiello > Assignee: Ramesh Reddy > Priority: Minor > > I've created a virtual table with a new field defined in this way: > select ROUND((BA.PREIS / BA.PEINH), 3) AS UnitPrice from xxxxxx > for the source field are bigdecimal I define UnitPrice as > BigDecimal (13,3) > If I run the qery from JDBC > select * from PurchaseRequisitionEntity where PurchaseRequisitionKey = '300-8000001452-00010' ; > PREIS = 539,568 > PEINH = 106 > UnitPrice = 5,090.264 > And the result is correct. If I run from odata2 > /odata/CASALE.1/Entities.PurchaseRequisitionEntity('300-8000001452-00010')?$format=json > "UnitPrice" : "5090.2640000000000000" > As you can see the field is rounded to the 3rd digit but 13 more digits are returned with 0 value. > Anyway odata2 succeeds in returning the result without errors. > With odata4 I get an error: > /odata4/CASALE.1/Entities/PurchaseRequisitionEntity('300-8000001452-00010')?$format=json > {"error":{"code":null,"message":"The value '5090.2640000000000000' is not valid for property 'UnitPrice'."}} > I think that's because the length of the field is greater then the matedata definition. > At the moment the only solution I can imagine is to convert the number to a string in the proper format and the parse it into a number -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 2016