[GitHub] gianm commented on issue #6827: DruidSchema and SystemSchema should avoid creating temprorary collections of the cardinality of all segments

[GitBox <gi...@apache.org>]

gianm commented on issue #6827: DruidSchema and SystemSchema should avoid creating temprorary collections of the cardinality of all segments
URL: https://github.com/apache/incubator-druid/issues/6827#issuecomment-452770096
 
 
   I don't think it should be gigabytes of data, right? Assuming the collections are using references to existing objects and not copies of them, it should be a few hundred MB at worst. But yeah, it'd be good to avoid creating all-segment-sized collections to the degree possible, even if the objects are shared.
   
   What are the kinds of concurrency bugs you think might be likely to introduce when avoiding allocations in these methods? Would be helpful to know what you're thinking so they can be more easily avoided.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org