heers
------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sease.io <http://sease.io/>
LinkedIn <https://linkedin.com/com
ck to working on the task I'll be able to elaborate more!
Cheers
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Sourc
I'll elaborate more when I go back to the task!
Cheers
----------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
you
updated!
I agree this would be useful in Learning To Rank and Hybrid Search in
general.
The current original score feature is unlikely to be useful if not
normalised per an estimated maximum score.
Cheers
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr
That's cool Mike! Well done!
On Wed, 21 Feb 2024, 22:02 Anshum Gupta, wrote:
> This is great! Like always, thank you Mike!
>
> On Mon, Feb 19, 2024 at 8:40 AM Michael McCandless <
> luc...@mikemccandless.com> wrote:
>
>> Hi Team,
>>
>> ~1.5 years ago (August 2022) we migrated our Lucene issue tr
Welcome, Stefan!
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sease.io <http://sease
).
Cheers
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sease.io <http://sease.io/>
LinkedIn
But I hope we bring it in :)
----------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sease.io <http:
Hi,
we are finalizing https://github.com/apache/lucene/pull/12253, we got some
last-minute valuable review comments and we would like to apply the
suggestions and bring them in 9.x .
Cheers
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer
ed to merges when agreement if found!
Thanks to everyone involved!
------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open S
ld be very useful if everyone interested, expresses their
preference.
Have a good day!
------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Tra
ly enforce the
>>>> limit in any way that can't easily be circumvented by a user. The codec
>>>> already supports any size vector - it doesn't impose any limit. The way the
>>>> API is written you can *already today* create an index with max-int sized
&g
#createType and then
in org.apache.lucene.document.FieldType#setVectorAttributes (for both byte
and float variants).
This should help people vote, great!
Cheers
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail
ject, not mine or yours for that matters.
Cheers
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sea
ished).
------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sease.io <http://sease.io/>
LinkedIn <https:
Hi Marcus,
I am afraid at this stage Robert's opinion counts just as any other
opinion, a single vote for option 1.
We are collecting a community's feedback here, we are not changing any code
nor voting for a yes/no.
Once the voting is finished, we'll operate an action depending on the
community's
For simplicity's sake, let's consider Option 2 and 4 as equivalent as they
are not mutually exclusive and just differ on a minor implementation
detail.
On Tue, 16 May 2023, 10:24 Alessandro Benedetti,
wrote:
> Option 4 also aim to refactor the limit in an appropriate place for the
hether I really understand the difference between Option 2
> and Option 4, or is it just about implementation details?
>
> Thanks
>
> Michael
>
>
>
> Am 16.05.23 um 10:50 schrieb Alessandro Benedetti:
>
> Hi all,
> we have finalized all the options proposed
My vote goes to *Option 4*.
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sease.io <h
sted to perfect what the _default_ limit should be, but I've
not seen an argument _against_ configurability. Especially in this way --
a toggle that doesn't bind Lucene's APIs in any way.
I'll keep this [VOTE] open for a week and then proceed to the
implementation.
---
:
"Dimensions Limit for KNN vectors - Next Steps"
Just to collect the possible options we have and then vote.
Let's see how it goes.
Cheers
------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@se
heers
------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sease.io <http://sease.io/>
LinkedIn <https://linkedin.com/com
Solr, Elasticsearch, OpenSearch, and
any sort of plugin development
------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
We
ad.
If you have anything else to add, please use the old thread.
Cheers
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | O
Adding to cc Daniele who worked on this quite recently!
Cheers
On Tue, 2 May 2023, 21:12 Gus Heck, wrote:
> Was fishing around in parsers in solr and discovered that we have two
> different term and boost classes in Lucene. Is this really desirable? They
> are quite similar except one implement
That's great! And we were talking about this exactly here:
https://github.com/apache/lucene/pull/12169
It would also help with the new token filter :)
------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.b
day in our javadocs
>> that you need XXX heap if you index vectors with dimension Y, fanout X,
>> levels Z, etc.
>> >>
>> >> RAM used during merging is unaffected by dimensionality, but is
>> affected by fanout, because the HNSW graph (not the raw vectors) is m
GB heap without hitting OOMEs regardless of the
>>> > number of dimensions, and the feedback I'm seeing is that many users
>>> > are still interested in indexing multi-million vector datasets despite
>>> > the slow indexing rate. I wish we could do better, a
y users
> > >> are still interested in indexing multi-million vector datasets despite
> > >> the slow indexing rate. I wish we could do better, and vector indexing
> > >> is certainly more expert than text indexing, but it still is usable in
>
I am very attentive to listen opinions but I am un-convinced here and I an
not sure that a single person opinion should be allowed to be detrimental
for such an important project.
The limit as far as I know is literally just raising an exception.
Removing it won't alter in any way the current perf
Yes, that was explicitly mentioned in the original mail, improving the
vector based search of Lucene is an interesting area, but off topic here.
Let's summarise:
- We want to at least increase the limit (or remove it)
- We proved that performance are ok to do it (and we can improve them more
in th
y blog)
>
> On Apr 6, 2023, at 8:57 AM, Alessandro Benedetti
> wrote:
>
> To be clear Robert, I agree with you in not bumping it just to 2048 or
> whatever not motivated enough constant.
>
> But I disagree on the performance perspective:
> I mean I am absolutely positive in w
index
> vectors with that many dimensions and it actually works and scales.
>
> On Thu, Apr 6, 2023 at 11:38 AM Alessandro Benedetti
> wrote:
> >
> > As I said earlier, a max limit limits usability.
> > It's not forcing users with small vectors to pay the perfor
>10 MB hard drive, wow I'll never need another floppy disk ever...
Neural nets... nice idea, but there will never be enough CPU power to run
them...
etc.
Is it possible to make it a configurable limit?
I think Gus is on spot, agree 100%.
Vector dimension is already configurable, it's the max di
> I don't know, Alessandro. I just wanted to point out the fact that by
Apache rules a committer's veto to a code change counts as a no-go.
Yeah Dawid, I was not provocative, I was genuinely asking what should a
pragmatic approach be to choose a limit/remove it, because I don't know how
to proceed
As I said earlier, a max limit limits usability.
It's not forcing users with small vectors to pay the performance penalty of
big vectors, it's literally preventing some users to use
Lucene/Solr/Elasticsearch at all.
As far as I know, the max limit is used to raise an exception, it's not
used to ini
Ok, so what should we do then?
This space is moving fast, and in my opinion we should act fast to release
and guarantee we attract as many users as possible.
At the same time I am not saying we should proceed blind, if there's
concrete evidence for setting a limit rather than another, or that a
ce
ve it.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Mon, Apr 3, 2023 at 9:51 AM Alessandro Benedetti
> wrote:
>
>> ... and what would be the next limit?
>> I guess we'll need to motivate it better than the 1024 one.
>> I apprec
t come down the road. Maybe someday we
> want to do product quantization and enforce that (k, m) both fit in a byte
> -- we wouldn't be able to do that if a vector's dimension were to exceed
> 32K.
>
> On Fri, Mar 31, 2023 at 11:57 AM Alessandro Benedetti <
> a.ben
tascience.stackexchange.com/questions/51404/word2vec-how-to-choose-the-embedding-size-parameter
> >>
> >> Having said this, we see various embedding services providing higher
> dimensions than 1024, like for example OpenAI, Cohere and Aleph Alpha.
> >>
> >&
n which is extremely
important for a library.
I strongly encourage people to add benefits and cons, that I missed (I am
sure I missed some of them, but wanted to keep it simple)
Cheers
------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache
Welcome, Ben!
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sease.io <http://sease.io/>
Li
+1
SUCCESS! [1:18:35.364317]
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sease.io <h
Done on main and cherry-picked on 9.x, thanks Luca for your patience!
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open
Yes Luca, doing it right now!
For Michael, it's just few getters.
Cheers
------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Tra
Hi,
this would be nice to have in 9.5 :
https://github.com/apache/lucene/issues/12099
It's a minor (adding getters to KnnQuery) but can be beneficial in Apache
Solr as soon as possible.
Planning to merge in a few hours if no objections.
------
*Alessandro Benedetti*
Dir
und!
This message is meant to be for anyone tonight in Tokyo, not necessarily
committers/PMC members!
Have a good one!
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information
ating the issue,
it would be much easier in the future to quickly find the latest happening
in the field(being an area that is super active).
Being involved in this area, I find it super useful!
Thanks for helping!
Cheers
------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apa
Benvenuto a bordo Luca ;)
On Thu, 6 Oct 2022, 06:27 Luca Cavanna, wrote:
> Thanks all for the warm welcome, I am thrilled to become a Lucene
> committer, thanks for the opportunity.
>
> A bit about me: I have been working at Elastic for a bit longer than 9
> years, where I contributed to many di
Welcome, Chris!
Cheers
--
*Alessandro Benedetti*
CEO @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sease.io <http://sease
Welcome on board Xugang!
--
*Alessandro Benedetti*
CEO @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benede...@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sease.io <http://sease
+1(committer, non PMC)
Lately I kinda feel having to create the Jira, after I detailed a
contribution in the pull request, is just a boilerplate activity of copying
and pasting and tagging again.
I would be happy to reduce this burden.
I left other details in the discussion thread.
Cheers
On Tu
ng removing the necessity of the (pretty annoying and
error-prone) "CHANGES.txt", and wondering if Jira could automatically solve
that necessity.
If GitHub is better at that, could be a strong incentive to go in that
direction!
Cheers
--
*Alessandro Benedetti*
Thanks Michael for the amazing work last year!
Welcome Bruno, I am sure you'll do great!
Cheers
On Thu, 24 Mar 2022, 09:23 Uwe Schindler, wrote:
> Hi,
>
> Thanks Michael for all the hard work last year.
> Welcome Bruno!
>
> Uwe
>
> -
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://
wn risk), we'll involve
also Michael Sokolov and the other committers familiar with this area of
the code.
Cheers
------
Alessandro Benedetti
Apache Lucene/Solr PMC member and Committer
Director, R&D Software Engineer, Search Consultant
www.sease.io
On Sat, 12 Fe
h-document-expansion.html
Cheers
------
Alessandro Benedetti
Apache Lucene/Solr PMC member and Committer
Director, R&D Software Engineer, Search Consultant
www.sease.io
On Tue, 15 Feb 2022 at 09:10, Michael Wechner
wrote:
> fair enough, but wouldn't i
Hi Michael, experience to what extent?
We have been exploring the area for a while given we contributed the first
neural search milestone to Apache Solr.
What is your curiosity? Performance? Relevance impact? How to integrate it?
Regards
On Fri, 11 Feb 2022, 22:38 Michael Wechner,
wrote:
> Hi
>
Welcome onboard Guo!
--
Alessandro Benedetti
Apache Lucene/Solr PMC member and Committer
Director, R&D Software Engineer, Search Consultant
www.sease.io
On Tue, 1 Feb 2022 at 23:34, Martin Gainty wrote:
> Welcome Guo !
>
Congratulations and welcome Haoyu!
--
Alessandro Benedetti
Apache Lucene/Solr Committer
Director, R&D Software Engineer, Search Consultant
www.sease.io
On Wed, 5 Jan 2022 at 17:32, Julie Tibshirani wrote:
> Welcome Patrick 🎉
>
> Julie
>
> On Wed,
Congrats Michael!
--
Alessandro Benedetti
Apache Lucene/Solr Committer
Director, R&D Software Engineer, Search Consultant
www.sease.io
On Fri, 19 Feb 2021 at 05:35, Melcom87s
wrote:
> Congrats!
>
>
>
> -
> ᐅ Targeted Web Traffic AFFORDABLE
Congrats Jan!
--
Alessandro Benedetti
Apache Lucene/Solr Committer
Director, R&D Software Engineer, Search Consultant
www.sease.io
On Fri, 19 Feb 2021 at 07:23, David Smiley wrote:
> Congratulations Jan!
>
> ~ David Smiley
> Apache Lucene/Solr Search
+1 Thanks Ishan for volunteering, much appreciated!
--
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
www.sease.io
On Sat, 19 Dec 2020 at 19:21, Bruno Roustant
wrote:
> +1 Thanks for volunteering
>
> Le ven. 18 déc. 2020 à
Hi,
I noticed the Apache Solr twitter account not to be that active anymore.
There are not even a tweet - > release 1 to 1 matching.
Not to mention the countless interesting blog posts Solr related, that
could benefit the community if better shared.
In my opinion, that's a shame, given the good nu
against using Jira to automate the changes generation either.
Cheers
--
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
www.sease.io
On Fri, 4 Dec 2020 at 16:57, Robert Muir wrote:
> I think the goal would be to minimize this editing,
Welcome onboard Julie!
--
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
www.sease.io
On Thu, 19 Nov 2020 at 03:23, Tomás Fernández Löbbe
wrote:
> Welcome Julie!
>
> On Wed, Nov 18, 2020 at 6:59 PM Ilan Ginzburg wrote:
>
>
I really appreciate that.
I am going to commit the changes soon unless anyone objects/provide some
additional review.
I'll wait one week more and then I'll proceed.
Cheers
--
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
www.sease.io
Didn't get any success so far, is anyone aware of the correct procedure to
ask INFRA for the permission check/ account merge?
Cheers
--
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
www.sease.io
On Sun, 21 Jun 2020 at 14:48, Alessandro
For your reference: https://issues.apache.org/jira/browse/INFRA-20455
--
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
www.sease.io
On Sun, 21 Jun 2020 at 13:47, Alessandro Benedetti
wrote:
> Thanks David,
> I appreciate your help.
Thanks David,
I appreciate your help.
I tried various approaches, all unsuccessful.
Created an INFRA ticket.
Hoping it helps.
Have a nice sunday!
Regards
--
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
www.sease.io
On Mon, 15 Jun 2020 at 1
Hi, I just tried to edit :
https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes#SolrTLPneededchanges-resolutionDraftboardresolution
But I couldn't manage to do that, is it something I am missing?
Do I need to register in someway in confluence? (I registered with the
apache e
together :)
Cheers
------
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
www.sease.io
On Wed, 18 Mar 2020 at 13:00, David Smiley wrote:
> Hi all,
>
> Please join me in welcoming Alessandro Benedetti as the latest Lucene/Solr
> committer!
>
> Alessandro has been
[
https://issues.apache.org/jira/browse/SOLR-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Benedetti updated SOLR-13663:
Description:
Currently the XML Query Parser support a vast array of span queries
[
https://issues.apache.org/jira/browse/SOLR-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896141#comment-16896141
]
Alessandro Benedetti commented on SOLR-13663:
-
Ready for review
> XM
[
https://issues.apache.org/jira/browse/SOLR-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Benedetti updated SOLR-13663:
Attachment: SOLR-13663.patch
> XML Query Parser to Support SpanPositionRangeQu
[
https://issues.apache.org/jira/browse/SOLR-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Benedetti updated SOLR-13663:
Status: Patch Available (was: Open)
> XML Query Parser to Supp
Alessandro Benedetti created SOLR-13663:
---
Summary: XML Query Parser to Support SpanPositionRangeQuery
Key: SOLR-13663
URL: https://issues.apache.org/jira/browse/SOLR-13663
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-9095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16879398#comment-16879398
]
Alessandro Benedetti commented on SOLR-9095:
Brilliant, thank you very
[
https://issues.apache.org/jira/browse/SOLR-9095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16879335#comment-16879335
]
Alessandro Benedetti edited comment on SOLR-9095 at 7/5/19 2:4
[
https://issues.apache.org/jira/browse/SOLR-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16879337#comment-16879337
]
Alessandro Benedetti commented on SOLR-7830:
Any update on this issue? I
[
https://issues.apache.org/jira/browse/SOLR-9095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16879335#comment-16879335
]
Alessandro Benedetti commented on SOLR-9095:
[~munendrasn] , tou resolve
[
https://issues.apache.org/jira/browse/SOLR-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853002#comment-16853002
]
Alessandro Benedetti commented on SOLR-12304:
-
That's great!
[
https://issues.apache.org/jira/browse/LUCENE-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841220#comment-16841220
]
Alessandro Benedetti commented on LUCENE-8326:
--
Anyone intereste
[
https://issues.apache.org/jira/browse/LUCENE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837163#comment-16837163
]
Alessandro Benedetti commented on LUCENE-6687:
--
Thanks [~teofili]
[
https://issues.apache.org/jira/browse/SOLR-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753905#comment-16753905
]
Alessandro Benedetti commented on SOLR-12812:
-
Hi [~dweiss], the Cloud
[
https://issues.apache.org/jira/browse/SOLR-13172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753871#comment-16753871
]
Alessandro Benedetti commented on SOLR-13172:
-
Hi [~dweiss], this is a
[
https://issues.apache.org/jira/browse/SOLR-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753857#comment-16753857
]
Alessandro Benedetti commented on SOLR-12304:
-
The bot doesn't
[
https://issues.apache.org/jira/browse/SOLR-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753858#comment-16753858
]
Alessandro Benedetti commented on SOLR-12304:
-
The bot doesn't
[
https://issues.apache.org/jira/browse/LUCENE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753856#comment-16753856
]
Alessandro Benedetti commented on LUCENE-6687:
--
The bot doesn't
[
https://issues.apache.org/jira/browse/SOLR-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Benedetti updated SOLR-12304:
Attachment: SOLR-12304.patch
> Interesting Terms parameter is ignored by
[
https://issues.apache.org/jira/browse/LUCENE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Benedetti updated LUCENE-6687:
-
Attachment: LUCENE-6687.patch
> MLT term frequency calculation
[
https://issues.apache.org/jira/browse/LUCENE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753458#comment-16753458
]
Alessandro Benedetti commented on LUCENE-6687:
--
Pull request and p
[
https://issues.apache.org/jira/browse/LUCENE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Benedetti updated LUCENE-6687:
-
Attachment: LUCENE-6687.patch
> MLT term frequency calculation
[
https://issues.apache.org/jira/browse/SOLR-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Benedetti updated SOLR-12304:
Attachment: SOLR-12304.patch
> Interesting Terms parameter is ignored by
[
https://issues.apache.org/jira/browse/SOLR-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753377#comment-16753377
]
Alessandro Benedetti commented on SOLR-12304:
-
Hi [~dsmiley], I created
[
https://issues.apache.org/jira/browse/SOLR-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753375#comment-16753375
]
Alessandro Benedetti commented on SOLR-12304:
-
[~dsmiley], I just cre
Alessandro Benedetti created SOLR-13172:
---
Summary: Deprecate MoreLikeTHisHandler
Key: SOLR-13172
URL: https://issues.apache.org/jira/browse/SOLR-13172
Project: Solr
Issue Type
[
https://issues.apache.org/jira/browse/SOLR-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738355#comment-16738355
]
Alessandro Benedetti commented on SOLR-12304:
-
thanks for your resp
[
https://issues.apache.org/jira/browse/SOLR-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737213#comment-16737213
]
Alessandro Benedetti commented on SOLR-12304:
-
[~dsmiley] any feedbac
[
https://issues.apache.org/jira/browse/SOLR-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722863#comment-16722863
]
Alessandro Benedetti commented on SOLR-12304:
-
I will just repeat my
35422
[2] https://issues.apache.org/jira/browse/SOLR-12238
--
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
www.sease.io
On Wed, Nov 21, 2018 at 2:34 AM Michael Sokolov wrote:
> This is a great idea. It would also be compelling to modify the term
>
1 - 100 of 495 matches
Mail list logo
