[
https://issues.jboss.org/browse/TEIID-5574?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5574:
---------------------------------------
No not really, as you say they are behind the EmbeddedConfiguration,
does not really matter.
Can you clarify that you currently map the spring config to the EmbeddedConfiguration so
that is where we need the method names to line up with the expected convention? I'm
assuming that below.
If all the properties are related to buffer manager exclusively then
the below makes sense to me
The user level proposal would be to have the EmbeddedConfiguration methods via the spring
convention and the cli properties match - so that anything that any message that currently
references a cli property can be generic to both? Cli properties are currently prefixed
as buffer-service, but moving forward can all be buffer-manager along with any
clarification, units, and reordering such that they are more logically grouped.
Clarify buffer manager property names
-------------------------------------
Key: TEIID-5574
URL:
https://issues.jboss.org/browse/TEIID-5574
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine, Server
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.0
Where possible the buffer manager properties should be better differentiated. Instead of
max-buffer-space for example, we could have max-buffer-disk-space-mb.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)