[
https://issues.jboss.org/browse/TEIID-5574?page=com.atlassian.jira.plugin...
]
Ramesh Reddy edited comment on TEIID-5574 at 12/18/18 5:06 PM:
---------------------------------------------------------------
How are you proposing this will map to spring?
No not really, as
you say they are behind the EmbeddedConfiguration, does not really matter.
Perhaps the question is how will work from a user perspective.
Yes, this is the angle I have been thinking.
If all the properties are related to buffer manager exclusively then the below makes sense
to me
{code}
bufferManagerHeapMemory[???]
bufferManagerFixedMemory[???]
bufferManagerDisk[???]
{code}
was (Author: rareddy):
How are you proposing this will map to spring?
No not really, as
you say they are behind the EmbeddedConfiguration, does not really matter.
Perhaps the question is how will work from a user perspective.
Yes, this is the angle I have been thinking.
If all the properties are related to buffer manager exclusively then the below makes sense
to me
bufferManagerHeapMemory{...}
bufferManagerFixedMemory{...}
bufferManagerDisk{...}
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)