[JBoss JIRA] Created: (TEIID-1492) StackOverflowError in DefaultCache
by Mark Addleman (JIRA)
StackOverflowError in DefaultCache
----------------------------------
Key: TEIID-1492
URL: https://issues.jboss.org/browse/TEIID-1492
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.2
Environment: Windows & Linux
Reporter: Mark Addleman
Assignee: Steven Hawkins
Intermittently, we get the stack overflow error. It doesn't seem to be related to the query.
java.lang.StackOverflowError
at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164)
at org.teiid.cache.DefaultCache.validate(DefaultCache.java:119)
at org.teiid.cache.DefaultCache.access$000(DefaultCache.java:36)
at org.teiid.cache.DefaultCache$1.removeEldestEntry(DefaultCache.java:86)
at java.util.LinkedHashMap.putImpl(LinkedHashMap.java:411)
at java.util.LinkedHashMap.put(LinkedHashMap.java:370)
at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164)
at org.teiid.cache.DefaultCache.validate(DefaultCache.java:119)
at org.teiid.cache.DefaultCache.access$000(DefaultCache.java:36)
at org.teiid.cache.DefaultCache$1.removeEldestEntry(DefaultCache.java:86)
at java.util.LinkedHashMap.putImpl(LinkedHashMap.java:411)
at java.util.LinkedHashMap.put(LinkedHashMap.java:370)
at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164)
at org.teiid.cache.DefaultCache.validate(DefaultCache.java:119)
at org.teiid.cache.DefaultCache.access$000(DefaultCache.java:36)
at org.teiid.cache.DefaultCache$1.removeEldestEntry(DefaultCache.java:86)
at java.util.LinkedHashMap.putImpl(LinkedHashMap.java:411)
at java.util.LinkedHashMap.put(LinkedHashMap.java:370)
at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164)
at org.teiid.cache.DefaultCache.validate(DefaultCache.java:119)
at org.teiid.cache.DefaultCache.access$000(DefaultCache.java:36)
at org.teiid.cache.DefaultCache$1.removeEldestEntry(DefaultCache.java:86)
at java.util.LinkedHashMap.putImpl(LinkedHashMap.java:411)
at java.util.LinkedHashMap.put(LinkedHashMap.java:370)
at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (TEIID-1473) Don't batch more rows than is needed when query contains limit but translator does not support limit
by Howard Abrams (JIRA)
Don't batch more rows than is needed when query contains limit but translator does not support limit
----------------------------------------------------------------------------------------------------
Key: TEIID-1473
URL: https://issues.jboss.org/browse/TEIID-1473
Project: Teiid
Issue Type: Enhancement
Reporter: Howard Abrams
Assignee: Steven Hawkins
Priority: Minor
Teiid shouldn't try to batch more rows than is needed when query contains limit and translator does not support limit.
For example, say there is a translator that exposes a table "A", but does not support limit.
select * from A limit 2
will currently select an entire batch of rows (1024?) from A, instead of just stopping after 2 rows.
Likewise, if the translator supports neither offset nor limit, and the query contains both, Teiid should not try to batch more that (offset + limit) rows.
This is marked as "Minor" because the workaround of naively supporting limit and offset within a translator is not too hard.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Updated: (TEIID-1550) Row level security enhancements
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1550?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-1550:
----------------------------------
Description:
To assist with implementing row level security through UDFs the following enhancements are requested:
1. Add the ability for data roles to cover functions.
2. Add the ability to get the JAAS subject from the CommandContext so that UDFs can perform attribute or other checks on the subject easily.
Actual row level security will then be up to the implementer of the UDF.
was:
Requesting Row level security model to restrict user access to sensitive information defining new Security Domain in SOA Platform configured to use XACML authorization. Specification of Business Rules that will restrict access to data at a row level based on User Profile attributes like cost center, roles, portfolio.
Currently this is not available for system or User Defined Functions, just tables. Requesting that this capability be added.
Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes]
To clarify there is nothing here that is a built in feature related to row level security. The customer logged the issue through GSS with a description of what they were thinking. Additional requests for details found that they didn't yet have a full implementation path, but would at least want enhancements listed in the description/resolution.
> 1. How is row level security turned on/off
There is no specific feature related to row level security to turn on/off.
> 2. Is this a System function that can be called in a transformation
Other than the existing hasRole/user functions, no.
> 3. What happens if the user doesn't have access, is an exception thrown, the column removed or data nulled out (and are there options to control the behavior)
N/A
> Row level security enhancements
> -------------------------------
>
> Key: TEIID-1550
> URL: https://issues.jboss.org/browse/TEIID-1550
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Labels: 7.4Beta3
> Fix For: 7.4
>
>
> To assist with implementing row level security through UDFs the following enhancements are requested:
> 1. Add the ability for data roles to cover functions.
> 2. Add the ability to get the JAAS subject from the CommandContext so that UDFs can perform attribute or other checks on the subject easily.
> Actual row level security will then be up to the implementer of the UDF.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Commented: (TEIID-1550) Row level security enhancements
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-1550?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-1550:
------------------------------------
Couple of questions:
1. How is row level security turned on/off
2. Is this a System function that can be called in a transformation
3. What happens if the user doesn't have access, is an exception thrown, the column removed or data nulled out (and are there options to control the behavior)
> Row level security enhancements
> -------------------------------
>
> Key: TEIID-1550
> URL: https://issues.jboss.org/browse/TEIID-1550
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Labels: 7.4Beta3
> Fix For: 7.4
>
>
> Requesting Row level security model to restrict user access to sensitive information defining new Security Domain in SOA Platform configured to use XACML authorization. Specification of Business Rules that will restrict access to data at a row level based on User Profile attributes like cost center, roles, portfolio.
> Currently this is not available for system or User Defined Functions, just tables. Requesting that this capability be added.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months