April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2311) Add simple row based security to data roles

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2311?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2311. --------------------------------- > Add simple row based security to data roles > ------------------------------------------- > > Key: TEIID-2311 > URL: https://issues.jboss.org/browse/TEIID-2311 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > A common request is to implement row based security. The common workaround of modifying transformations is generally not a good solution. > We should look at adding support for simple table filters and column masks. > To be effective, filtering permissions however would have to act differently than normal data roles. They would need to be applied all the time - and not just against the end user queries. > For example, for tables: > <permission> > <resource-name>SCHEMA.TABLE</resource-name> > <filter>COLUMNA=2</filter> > </permission> > Meaning allow the CRUD of the given row only if COLUMNA has the value of 2. Any valid predicate against just the referenced table would be allowed as a filter. Each such permission would be applied as an additional predicate any time the table is referenced (in views, inserts, updates, deletes, etc.). > Allows would not be specified here as we want the filter to always specify inclusion. Any applicable permissions in additional roles would be applied disjunctively - filter OR filter. > We could possibly support column masks via case expressions, such as: > <permission> > <resource-name>SCHEMA.TABLE.COLUMN</resource-name> > <mask>CASE WHEN ...</mask> > </permission> > However this is slightly more complicated. Presumably the mask would only apply to projection and makes more sense to be applied at the final output/user query (more like a data role). > If we work the issue to specify the object type of a permission, then the name could alternatively refer to datatype or even an extension property to make the masking a little easier. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2526) When VDB re-deployed with same version the the OData metadata does not reflect the new VDB metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2526?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2526. --------------------------------- > When VDB re-deployed with same version the the OData metadata does not reflect the new VDB metadata > --------------------------------------------------------------------------------------------------- > > Key: TEIID-2526 > URL: https://issues.jboss.org/browse/TEIID-2526 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: CR2 > Fix For: 8.4 > > > When the same named VDB is re-deployed with same version as before, the call to > http://host:port/odata/vdb/$metadata > does not reflect the new metadata of the re-deployed VDB -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2893) Add support for EAP 6.3

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2893?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2893: ------------------------------------- If 6.2 support also need that needs to be tracked in separate JIRA > Add support for EAP 6.3 > ----------------------- > > Key: TEIID-2893 > URL: https://issues.jboss.org/browse/TEIID-2893 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits, Server > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 8.7.1 > > > Add support for EAP 6.2 or 6.3. The final version will not be known until EAP 6.3 release date is known. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1941) Coherence Translator/Connector - Add the ability to issue UPDATE statements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1941?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1941. --------------------------------- > Coherence Translator/Connector - Add the ability to issue UPDATE statements > --------------------------------------------------------------------------- > > Key: TEIID-1941 > URL: https://issues.jboss.org/browse/TEIID-1941 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Van Halbert > > Add the ability to support UPDATE statements -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1465) Join between char and varchar

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1465?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1465. --------------------------------- > Join between char and varchar > ----------------------------- > > Key: TEIID-1465 > URL: https://issues.jboss.org/browse/TEIID-1465 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.3 > Environment: Teiid 7.3 deployed on Jboss AS 5.1.0 GA running on Ubuntu Server 10.04 LTS, MySQL 5.1.51 running on the same machine as JBoss, SQL Server 2000 Standard SP4 running on Windows Server 2003 > Reporter: Claudio Venturini > Assignee: Steven Hawkins > Labels: char, join, varchar > Fix For: 7.7, 8.0 > > > Joins between char and varchar fields fail. > Suppose to have a table T1 with a field A, declared as char(10), and a table T2 with a field B, declared as varchar(10). Suppose that the two tables have the following data. > *T1*: > ||A|| > |ML0001| > *T2*: > ||B|| > |ML0001| > When performing a INNER JOIN with the condition {{T1.A = T2.B}} the result set is empty, even if the two record match correctly. > This happens when the two base tables refer to two different sources, because if they are in the same source Teiid pushes the join to the source, which computes it correctly. > I think the problem is in the comparison of the two strings. I have the table T1 in SQL Server 2000, and the table T2 in MySQL 5.1. > If one asks SQL Server to convert the string to bytes, the result is {{0x4D4C3030303120202020}}, because the string is filled with (invisible) blanks in order to reach the limit of 10 characters. Note that if one asks for the length of that string, SQL Server states (correctly) that it is 6 characters. > The string in MySQL is a VARCHAR(10), so its conversion to binary is {{0x4D4C30303031}}. > I think that Teiid compares the two binary strings in their entire length. That comparison fails, and no match is found. > The problem remains even if the table T1 is placed in MySQL, and T2 in SQL Server (the opposite situation). I also verified that the problem exists either when querying the source models or view models built over them. > *Workaround:* > A workaround exists but it is too complex (IMHO). I haven't tested it with many records, but I think it will slow down performances considerably. > It consists in casting the string from char to varchar, and then trimming it (with RTRIM() and LTRIM() because SQL Server doesn't support TRIM()). So the join condition is: > {noformat} > RTRIM(LTRIM(CAST(T1.A AS VARCHAR))) = T2.B > {noformat} -- 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, 11 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2471?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2471. --------------------------------- > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1522) propagate all projected constants from non-merged view layers

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1522?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1522. --------------------------------- > propagate all projected constants from non-merged view layers > ------------------------------------------------------------- > > Key: TEIID-1522 > URL: https://issues.jboss.org/browse/TEIID-1522 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.5 > > > For non-merged view layers there are planning and costing benefits to propagating any projected constants upward in the plan. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2837) Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name

by Ivan Chan (JIRA)

[ https://issues.jboss.org/browse/TEIID-2837?page=com.atlassian.jira.plugin... ] Ivan Chan commented on TEIID-2837: ---------------------------------- Sure. Thanks for looking. https://issues.jboss.org/browse/TEIID-2932 > Cassandra: doesn't work with Case Sensitvie KEYSPACE and TABLE name > -------------------------------------------------------------------- > > Key: TEIID-2837 > URL: https://issues.jboss.org/browse/TEIID-2837 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.6 > Environment: Cassandra with Teiid 8.6 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > Fix For: 8.7 > > > Teiid doesn't work with KeySpace or Table which contains UpperCase. > Reference From Cassandra - Using double quote for Case Sensitive KeySpace and Table: > http://www.datastax.com/docs/1.1/references/cql/CREATE_KEYSPACE > Exception when try to deploy: > java.lang.NullPointerException > at org.teiid.translator.cassandra.metadata.CassandraMetadataProcessor.processMetadata(CassandraMetadataProcessor.java:52) > at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:100) > at org.teiid.translator.cassandra.CassandraExecutionFactory.getMetadata(CassandraExecutionFactory.java:53) > at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61) > at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:644) > at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:161) > at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:605) > at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:536) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2893) Add support for EAP 6.3

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2893?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2893: -------------------------------- Summary: Add support for EAP 6.3 (was: Add support for EAP 6.2/6.3) > Add support for EAP 6.3 > ----------------------- > > Key: TEIID-2893 > URL: https://issues.jboss.org/browse/TEIID-2893 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits, Server > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 8.7.1 > > > Add support for EAP 6.2 or 6.3. The final version will not be known until EAP 6.3 release date is known. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2677) Makedep keyword hint not displayed correctly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2677?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2677. --------------------------------- > Makedep keyword hint not displayed correctly > -------------------------------------------- > > Key: TEIID-2677 > URL: https://issues.jboss.org/browse/TEIID-2677 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > If an extended makedep keyword hint is used int the from clause: > from x makedep(join) ... > it will be displayed in the comment hint as: > from /+* makedep(join) */ x ... > which is not recognized by the parsing logic. -- 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, 11 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 April 2014