Re: Bulk indexing and delete old index files
Hi, I did it with Erick's solution. I did mark index file versions to all documents and delete old documents before index new documents. If documents are just update or add, you can use 'automatically replaced' strategy with document's unique key. Thanks. 2013/12/2 revolutionizeit > Did you get this working? Are you able to share the solution? > > I am looking for a solution to similar problem. > > Thanks in advance. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Bulk-indexing-and-delete-old-index-files-tp4044746p4104297.html > Sent from the Lucene - Java Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > -- DEV용식 http://devyongsik.tistory.com
Re: Where is the source for the .dat files in Kuromoji?
On Dec 3, 2013, at 8:38 AM, Benson Margulies wrote: > I'm not clear that there's anything that anyone would complain of. The > question is, are the .dat files part of the source bundle that is the > 'official release'? I just fetched from git, not from the official release, > so I don't know. I’d say the .dat files are part of the source bundle, which is the ‘official release’, but PMCs feel free to chime in... The .dat files have been checked into SVN in binary form to make Lucene easy to build and they’re also rather modest in size thanks to squeezing work done by Robert and Uwe. Best, Christian - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
SortingMergePolicy for index-block-joins
I am trying to find an optimal way of merging two already sorted segments and need some help here... My use-case is this: Segment1 [Segment already sorted by Field "F1"] Fields: F1, F2, F3 List Fields: C1, C2 Segment2 [Segment already sorted by Field "F1"] Fields: F1, F2, F3 List Fields: C1, C2 I want to merge individually-sorted Segment1 & Segment2 based on field "F1". SortingMergePolicy will greatly help here. But if you notice, my child-docs don't have field "F1". Will it work correctly? Another doubt I had was, since these 2 segments are individually-sorted, is it possible to merge these 2 segments with a leap-frog-enumerator [based on field F1] instead of SortingMergePolicy? -- Ravi
