It's not trivial for users to know when to add an index. It definitely improves the experience if they can easily add/remove indexes. Regarding storage, indexes can be quite big depending on the cardinality for e.g. inv index on something like memberId is not very useful.
On Tue, Feb 11, 2020 at 5:07 PM Mayank Shrivastava <[email protected]> wrote: > Subbu, I think the proposal is to reduce the storage cost, which is why I > asked how often is that seen (outside LinkedIn). > > Sent from my iPhone > > > On Feb 11, 2020, at 3:38 PM, Subbu Subramaniam <[email protected]> > wrote: > > > > I believe we do not map the index if it is not sset in the table > config, so the index is not loaded. > > > > The cost on storage exists, but hopefully is a lot smaller than memory. > > > > -Subbu > > > >> On 2020/02/11 22:37:13, kishore g <[email protected]> wrote: > >> Currently, we only support adding indices to the pinot segment. If the > >> index is removed from table config, we dont load it but continue to > keep it > >> in the segment. The only drawback with this is additional usage of disk > >> space. > >> > >> We should enhance the segment preprocessor to have the ability to > rewrite > >> the segment. > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
