That's certainly an option, but I was leaning the other way (making it work). I know of a user that is dividing up their data into frequently and less frequently (re)indexed stuff which is normally accessed by an alias and they presently have to query for the list of collections in the alias and then /get on each collection independently because of the current behavior. This works, and if we start producing an error, they can of course continue to do that, but it feels clumsy and inelegant for them to have to do that to me at least). Also, it might not be all bad if it worked with routed aliases.
On Fri, Sep 6, 2019 at 5:06 PM David Smiley <david.w.smi...@gmail.com> wrote: > On Wed, Sep 4, 2019 at 11:26 PM Gus Heck <gus.h...@gmail.com> wrote: > >> It seems that the real time get handler doesn't play nice with aliases. >> The current (and past) behavior seems to be that it only works for the >> first collection listed in the alias. This seems to be pretty clearly a >> bug, as one certainly would expect the /get executed against an alias to >> either refuse to work with aliases or work across all collections in the >> alias rather than silently working only on the first collection. >> > > I think it should just refuse to work (throw an exception) if there are > multiple collections in the alias -- simple. It's okay for components to > have a limitation. > > Solr's internal use of RTG isn't affected by this scenario. I believe few > users even use RTG but yes of course some do and I know of at least one. > In the one case I saw RTG used, it was an nice optimization that replaced > its former mode of operation that worked fine. > > ~ David > >> -- http://www.needhamsoftware.com (work) http://www.the111shift.com (play)
