milleruntime commented on pull request #1799:
URL: https://github.com/apache/accumulo/pull/1799#issuecomment-732423934


   > That said, because this would make all 4 columns fetched every time we 
want to fetch the CURRENT or FUTURE location, it might be better to leave LAST 
and create a new SUSPEND enum, so that way we only need to fetch the specific 
locations we need, and no more. It's a little weird that the LOCATION enum 
fetches both CURRENT and FUTURE locations, but only one should be set anyway, 
so it's probably fine.
   
   I realize now that LOCATION will only ever return one value from the two 
fetched columns (current or future).  So I agree, it would be better to keep it 
that way and add a new type for SUSPEND. 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to