Re: Finding out which fields matched the query

2022-06-26 Thread Jörn Franke
What is the reason you need the matched fields? Maybe your use case can be solved using sth completely different than knowing which fields were matched. > Am 25.06.2022 um 06:58 schrieb Yichen Sun : > > Hello! > > I’m a MSCS student from BU and learning to use Lucene. Recently I try to > outp

Re: A prototype migration tool Jira to GitHub

2022-06-26 Thread Tomoko Uchida
> It looks like the GitHub Danger Zone can transfer a repository? "Transferring a repository" creates another repository different from apache/lucene. It'd make the migration process easy though, is it our intention to have an external repository for old issues? Tomoko 2022年6月27日(月) 8:24 Michae

Re: A prototype migration tool Jira to GitHub

2022-06-26 Thread Michael McCandless
It looks like the GitHub Danger Zone can transfer a repository? It's not clear if it can go from Personal -> Organization though. I see Personal -> Personal and Organization -> Organization. https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository Mik

Re: A prototype migration tool Jira to GitHub

2022-06-26 Thread Tomoko Uchida
> > 2022年6月27日(月) 5:16 Michael Sokolov : > >> as for this access control/script monitoring problem, I wonder whether >> we could import all the issues into a new github repo owned by >> whomever is running the script, and then transfer from there to the >> lucene repo? It would be an extra step inv

Re: A prototype migration tool Jira to GitHub

2022-06-26 Thread Tomoko Uchida
2022年6月27日(月) 5:16 Michael Sokolov : > as for this access control/script monitoring problem, I wonder whether > we could import all the issues into a new github repo owned by > whomever is running the script, and then transfer from there to the > lucene repo? It would be an extra step involving an

Re: A prototype migration tool Jira to GitHub

2022-06-26 Thread Michael Sokolov
as for this access control/script monitoring problem, I wonder whether we could import all the issues into a new github repo owned by whomever is running the script, and then transfer from there to the lucene repo? It would be an extra step involving another script (or something), but maybe(?) that

Re: Finding out which fields matched the query

2022-06-26 Thread Shai Erera
Hi Yichen, I think you can implement a custom Collector which tracks the fields that were matched for each Scorer. I implemented an example such Collector below: public class FieldMatchingCollector implements Collector { /** Holds the number of matching documents for each field. */ public fi