Nikolay, I have not filed any ticket yet. I would like to discuss first.
> Yes, this was made intentionally. > I think we shouldn’t hide internal details from the user in the system views. Regarding proxy indices Cannot immediately agree here. My understanding is that the view in question should contain information which a user can use for managing SQL workflows. E.g. for a query optimization. From a (unit) test I cannot figure out how a proxy index is different from an underlying one from a user perspective. Could you please elaborate? Best regards, Ivan Pavlukhin пт, 7 февр. 2020 г. в 13:33, Nikolay Izhikov <nizhi...@apache.org>: > > > 1. Columns related to a cache group information disappeared. > > Information about cache group can be gathered from SYS.CACHES and > SYS.CACHE_GROUPS. > > > 2. "proxy" indexes info is now displayed in the view. > > Yes, this was made intentionally. > I think we shouldn’t hide internal details from the user in the system views. > > Please, note, that there is no Ignite release with index system view, for now. > > > 7 февр. 2020 г., в 13:26, Ivan Pavlukhin <vololo...@gmail.com> написал(а): > > > > Nikolay, > > > > Recently I noticed some changes in SQL indexes view content introduced > > in [1]. Among changes I noticed: > > 1. Columns related to a cache group information disappeared. > > 2. "proxy" indexes info is now displayed in the view. > > > > Was this changes made intentionally? Historically there were following > > tickets [2, 3] for indexes system views. And as [3] added a cache > > group info but [1] removed it makes me think that some changes appear > > not intentionally. From the first glance it seems to me that we should > > restore [3] behavior. Correct me if I am wrong. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12213 > > [2] https://issues.apache.org/jira/browse/IGNITE-11056 > > [3] https://issues.apache.org/jira/browse/IGNITE-11443 > > > > Best regards, > > Ivan Pavlukhin >
