[JBoss JIRA] (TEIID-2708) DataRolePolicyDecider configuration
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2708?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2708:
-------------------------------------
No, I do not know any such mechanism. Having user take responsibility for configuration was original intention, but the default module properties lot in translation.
> DataRolePolicyDecider configuration
> -----------------------------------
>
> Key: TEIID-2708
> URL: https://issues.jboss.org/browse/TEIID-2708
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.6
>
>
> In the conversion over to AS 7 the bean properties for DataRolePolicyDecider were not added to the configuration. More than likely this was because the bean itself is pluggable.
> We either need to add these properties to the configuration or add an alternative mechanism for setting them (system and/or vdb properties would probably be just fine).
--
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, 2 months
[JBoss JIRA] (TEIID-2707) proactive buffering on an enhanced sort merge left outer join results in an assertionerror
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2707?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2707.
-----------------------------------
Resolution: Done
Rewrote the prefetch logic to be more straight-forward and covered additional cases. Also removed the use of the prefetch limit and instead made it based upon the number of batches pulled from the other side. Will update the docs that the property is not currently used.
> proactive buffering on an enhanced sort merge left outer join results in an assertionerror
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-2707
> URL: https://issues.jboss.org/browse/TEIID-2707
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.6
>
>
> The proactive buffering logic with particular blocking patterns is not correct. Namely the setting of the buffer to forward only prevents re-reading which results in an AssertionError.
--
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, 2 months
[JBoss JIRA] (TEIID-2708) DataRolePolicyDecider configuration
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2708?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2708:
---------------------------------------
Do you know of a simple mechanism to mix-in some spring or other mc configuration to alter service loading?
It seems like explicit xml configuration for the possible built-in properties is the way to go otherwise. After more thought I guess I'd rather that the module owner take responsibility for their own configuration.
> DataRolePolicyDecider configuration
> -----------------------------------
>
> Key: TEIID-2708
> URL: https://issues.jboss.org/browse/TEIID-2708
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.6
>
>
> In the conversion over to AS 7 the bean properties for DataRolePolicyDecider were not added to the configuration. More than likely this was because the bean itself is pluggable.
> We either need to add these properties to the configuration or add an alternative mechanism for setting them (system and/or vdb properties would probably be just fine).
--
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, 2 months
[JBoss JIRA] (TEIID-2708) DataRolePolicyDecider configuration
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2708?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2708:
-------------------------------------
Yes, the module is self contained so we see such issues. I am not familiar with module properties, that seems like workable solution.
We could remove the default code based configuration, and add the same explicitly through xml configuration to provide a default template with properties if you want?
> DataRolePolicyDecider configuration
> -----------------------------------
>
> Key: TEIID-2708
> URL: https://issues.jboss.org/browse/TEIID-2708
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.6
>
>
> In the conversion over to AS 7 the bean properties for DataRolePolicyDecider were not added to the configuration. More than likely this was because the bean itself is pluggable.
> We either need to add these properties to the configuration or add an alternative mechanism for setting them (system and/or vdb properties would probably be just fine).
--
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, 2 months
[JBoss JIRA] (TEIID-2708) DataRolePolicyDecider configuration
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2708?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2708:
---------------------------------------
There doesn't seem to be a straight-forward out of the box way to set service properties. It may be possible to mix-in some spring configuration logic, but I'm not sure how the examples from web-apps transfer to the configuration.
One possibility is to rely on module properties - when we get a service instance we can inject properties declared in the corresponding module.xml. For mostly built-in services, such as the DataRolePolicyDecider, this mechanism alone isn't that desirable. Users would have to create their own module, import the engine, expose the same DataRolePolicyDecider service, and add the override properties.
> DataRolePolicyDecider configuration
> -----------------------------------
>
> Key: TEIID-2708
> URL: https://issues.jboss.org/browse/TEIID-2708
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.6
>
>
> In the conversion over to AS 7 the bean properties for DataRolePolicyDecider were not added to the configuration. More than likely this was because the bean itself is pluggable.
> We either need to add these properties to the configuration or add an alternative mechanism for setting them (system and/or vdb properties would probably be just fine).
--
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, 2 months
[JBoss JIRA] (TEIID-2708) DataRolePolicyDecider configuration
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2708:
-------------------------------------
Summary: DataRolePolicyDecider configuration
Key: TEIID-2708
URL: https://issues.jboss.org/browse/TEIID-2708
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.6
In the conversion over to AS 7 the bean properties for DataRolePolicyDecider were not added to the configuration. More than likely this was because the bean itself is pluggable.
We either need to add these properties to the configuration or add an alternative mechanism for setting them (system and/or vdb properties would probably be just fine).
--
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, 2 months