If we were designing things from scratch again, would boost really be on Query, or would it be on BooleanClause? Just throwing that out there... although it may make it easier to implement immutable queries (and perhaps make more sense too), it may also be too big of a change to be worth while.
-Yonik On Thu, Apr 2, 2015 at 9:27 AM, david.w.smi...@gmail.com <david.w.smi...@gmail.com> wrote: > On Thu, Apr 2, 2015 at 3:40 AM, Adrien Grand <jpou...@gmail.com> wrote: >> >> first make queries immutable up to the boost and then discuss >> if/how/when we should go fully immutable with a new API to change >> boosts? > > > The “if” part concerns me; I don’t mind it being a separate issue to make > the changes more manageable (progress not perfection, and all that). I’m > all for the whole shebang. But if others think “no” then…. will it have > been worthwhile to do this big change and not go all the way? I think not. > Does anyone feel the answer is “no” to make boosts immutable? And if so why? > > If nobody comes up with a dissenting opinion to make boosts immutable within > a couple days then count me as “+1” to your plans, else “-1” pending that > discussion. > > ~ David Smiley > Freelance Apache Lucene/Solr Search Consultant/Developer > http://www.linkedin.com/in/davidwsmiley --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
