April 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2474) Deploying dynamic VDB with invalid XML will cause incomprehensible error

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIID-2474?page=com.atlassian.jira.plugin... ] Filip Nguyen updated TEIID-2474: -------------------------------- Attachment: loop-vdb.xml > Deploying dynamic VDB with invalid XML will cause incomprehensible error > ------------------------------------------------------------------------ > > Key: TEIID-2474 > URL: https://issues.jboss.org/browse/TEIID-2474 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.3 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > Priority: Minor > Attachments: loop-vdb.xml > > > Deploying VDB with invalid XML (closed translator tag). Causes following error: > [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015009: Scan found incompletely copied file content for deployment standalone/deployments/loop-vdb.xml. Deployment changes will not be processed until all content is complete. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2169) Buffer Manger's memory should be backed by Infinispan Cache

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2169?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2169: ---------------------------------- Fix Version/s: (was: 8.4) Pulling out of 8.4 based upon the last comment as it would take some time for the necessary mechanisms to become available in Infinispan. A separate issue is how to handle mat view replication - if that is something we want do more via a different integration (for example modeshape) or modify our table logic to allow for page based replication and direct usage of infinispan rather than our current low level replication approach. > Buffer Manger's memory should be backed by Infinispan Cache > ----------------------------------------------------------- > > Key: TEIID-2169 > URL: https://issues.jboss.org/browse/TEIID-2169 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > > Currently the buffer manager uses the memory from the local VM's heap for processing the intermediate query results, anything that overruns is saved on the disk. Using this model so far proven very efficient. > However, when it comes to using the data grid as unlimited temp backing store where the results can be shared with other nodes in the case of fail-over of the session, this in current model does not work. By using the infinispan's local cache in standalone and replicated cache in distributed node for the buffer manager these issues can resolved. > Issues may be, currently Buffer Manager uses efficient btree based index store, also the uses file storage in block. To make it work, Teiid needs to have access to the Infinispan's eviction queue and may also needs to implement the cache store. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2470) Allow Embedded to use zip deployments

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2470?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2470: --------------------------------------- The changes here are pretty straight-forward, but we need to put some though into the VFS handling. The logic seems to require a temp location (even if mounted as a file instead of stream) so we can either add a temp location to the config or just write a read-only VFS zip Filesystem. > Allow Embedded to use zip deployments > ------------------------------------- > > Key: TEIID-2470 > URL: https://issues.jboss.org/browse/TEIID-2470 > Project: Teiid > Issue Type: Enhancement > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > With the generalization to support dynamic zip deployments, embedded should support a zip deployment as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2473) WHERE clause with contradicting condition should return no rows

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2473?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2473. ----------------------------------- Resolution: Duplicate Issue Duplicate of TEIID-2366 > WHERE clause with contradicting condition should return no rows > --------------------------------------------------------------- > > Key: TEIID-2473 > URL: https://issues.jboss.org/browse/TEIID-2473 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.1 > Environment: JZOS mainframe > Reporter: Jeff Hayes > Assignee: Steven Hawkins > Priority: Minor > > Using Eclipse datasource explorer with teiid connection using SHOWPLAN to demonstrate the problem. > Enter: SELECT * FROM SECURITY.SYSINFO WHERE SYSID = 'DE29 AND SYSID <> 'DE29' > USER COMMAND appears as: SELECT * FROM SECURITY.SYSINFO WHERE SYSID = 'DE29 > Apparently conflicting "AND SYSID <> 'DE29'" is dropped and I get results from SYSID = 'DE29'. > Enter: SELECT * FROM SECURITY.SYSINFO WHERE SYSID <> 'DE29' AND SYSID = 'DE29' > USER COMMAND appears as: SELECT * FROM SECURITY.SYSINFO WHERE 1 = 0 > And I get expected null result set. > Admittedly irrational query but it should give empty result set however you order the WHERE clause conditions. > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2473) WHERE clause with contradicting condition should return no rows

by Jeff Hayes (JIRA)

Jeff Hayes created TEIID-2473: --------------------------------- Summary: WHERE clause with contradicting condition should return no rows Key: TEIID-2473 URL: https://issues.jboss.org/browse/TEIID-2473 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 8.1 Environment: JZOS mainframe Reporter: Jeff Hayes Assignee: Steven Hawkins Priority: Minor Using Eclipse datasource explorer with teiid connection using SHOWPLAN to demonstrate the problem. Enter: SELECT * FROM SECURITY.SYSINFO WHERE SYSID = 'DE29 AND SYSID <> 'DE29' USER COMMAND appears as: SELECT * FROM SECURITY.SYSINFO WHERE SYSID = 'DE29 Apparently conflicting "AND SYSID <> 'DE29'" is dropped and I get results from SYSID = 'DE29'. Enter: SELECT * FROM SECURITY.SYSINFO WHERE SYSID <> 'DE29' AND SYSID = 'DE29' USER COMMAND appears as: SELECT * FROM SECURITY.SYSINFO WHERE 1 = 0 And I get expected null result set. Admittedly irrational query but it should give empty result set however you order the WHERE clause conditions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2472) Create quickstart(s) demonstrating security

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2472: ------------------------------------- Summary: Create quickstart(s) demonstrating security Key: TEIID-2472 URL: https://issues.jboss.org/browse/TEIID-2472 Project: Teiid Issue Type: Sub-task Components: Documentation Reporter: Steven Hawkins Fix For: 8.4 There should be quickstarts (or an expanded dataroles quickstart) covering row based security, column masking, and possibly the use of a udf that uses the subject, a credential mapping security domain, or credential pass-through to highlight other common scenarios. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2471) Allow permission conditions and masking to be pluggable

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2471: ------------------------------------- Summary: Allow permission conditions and masking to be pluggable Key: TEIID-2471 URL: https://issues.jboss.org/browse/TEIID-2471 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4 The AuthorizationValidator or similar interface should allow for alternative implementations to be plugged in for providing permission conditions and column masking. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2470) Allow Embedded to use zip deployments

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2470: ------------------------------------- Summary: Allow Embedded to use zip deployments Key: TEIID-2470 URL: https://issues.jboss.org/browse/TEIID-2470 Project: Teiid Issue Type: Enhancement Components: Embedded Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4 With the generalization to support dynamic zip deployments, embedded should support a zip deployment as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2467) thread waits for matview loads

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2467?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2467. ----------------------------------- Resolution: Done moved all temp logic over to stateful tuplesources that allow for proper blocking. This is somewhat more complicated than the previous logic since some of the operations now are nested (a blocking load of an imported mat view will have 3 tuplesources - the outer for the user query, the next for the creation of the temp table, and the inner for the view query). eventually we could also allow subquery evaluation with temp table queries - however that has additional considerations with read/write locks. > thread waits for matview loads > ------------------------------ > > Key: TEIID-2467 > URL: https://issues.jboss.org/browse/TEIID-2467 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > While a matview is loading other threads attempting to query the same matview are held as waiters on the table info lock. > Also the mat table loading thread is marked is not allowed to throw a blocked exception and is tied to the current loading work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2469) Load Materialised Views

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2469?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2469: ------------------------------------- +1 I did not think about that! Internally may be this way to accomplish it, based on a property defined in vdb.xml, or defined on table's OPTIONS property? > Load Materialised Views > ----------------------- > > Key: TEIID-2469 > URL: https://issues.jboss.org/browse/TEIID-2469 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.1 > Reporter: Gautam Banerjee > Assignee: Steven Hawkins > > Currently teiid does not load materialised views automatically. The request has to come for the materialised view or it has to be explicitly loaded. As materialised views are made with the purpose of preloading data, teiid should load the materialised views as default. There can be a tag or switch which will determine if the materialise views are to be preloaded or not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2013