[
https://issues.apache.org/jira/browse/SOLR-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015182#comment-16015182
]
ASF subversion and git services commented on SOLR-10413:
Commit
I did both from a clean slate several times on my local box, deleting
the entire data dir each time.
I may have some time tomorrow to see if I can get a test to fail. My
current working theory is that my test was too elementary since it
only indexed a couple of documents and if the "off by one"
[
https://issues.apache.org/jira/browse/SOLR-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cao Manh Dat updated SOLR-10413:
Attachment: SOLR-10413.patch
Updated patch, without reflection + oneOf validator. Will commit this
[
https://issues.apache.org/jira/browse/SOLR-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cao Manh Dat resolved SOLR-10434.
-
Resolution: Resolved
Resolved in SOLR-10431
> Create a new mapping for admin calls & non-admin
[
https://issues.apache.org/jira/browse/SOLR-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015108#comment-16015108
]
Noble Paul edited comment on SOLR-10413 at 5/18/17 2:38 AM:
bq. is more type
[
https://issues.apache.org/jira/browse/SOLR-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015108#comment-16015108
]
Noble Paul commented on SOLR-10413:
---
bq. is more type safe and less complex than reflection?
yes
> v2
[
https://issues.apache.org/jira/browse/SOLR-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015100#comment-16015100
]
David Smiley commented on SOLR-10702:
-
I can tell you that Woodstox is definitely optional to *SolrJ*;
[
https://issues.apache.org/jira/browse/SOLR-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015097#comment-16015097
]
Cao Manh Dat commented on SOLR-10413:
-
I don't think
{code}
+ static final Map
Behavior 1: I don't think this is expected at all. You could raise a
JIRA... but I wonder what's going on in the particular environment where
you're seeing this that may be related. So trying to reproduce it in a
JUnit test is next (I think). Or try manually from a clean slate. You said
you
[
https://issues.apache.org/jira/browse/SOLR-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-10413:
--
Attachment: SOLR-10413.patch
The map usage is type safe and less complex
> v2 API: parsed JSON type
On Wed, May 17, 2017 at 7:36 PM Mike Drob wrote:
> David, what do you mean by
>
> > Hopefully without generating comments that trigger email/watcher
> notifications and thus no more dev list traffic.
>
> How else other than a comment could the system communicate results back to
informal +1 - just fired up this RC1 and all was well with the payload support
(SOLR-1485) with my use-case scripts.
Erik
> On May 17, 2017, at 9:49 AM, Ishan Chattopadhyaya wrote:
>
> Please vote for release candidate 1 for Lucene/Solr 6.6.0
>
> The artifacts can
[
https://issues.apache.org/jira/browse/SOLR-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015041#comment-16015041
]
Tomás Fernández Löbbe commented on SOLR-10233:
--
Just pushed some more changes to the branch.
> This could be a submitter changing state to "Patch Available" or could be
a naming convention
Yes, I was thinking on something along those lines too. I've also seen
tools triggering by specific comments in Jira. Any way is fine with me.
> If the state is set automatically, how do we know when to
[
https://issues.apache.org/jira/browse/SOLR-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015011#comment-16015011
]
Cao Manh Dat commented on SOLR-10413:
-
I disagree with using map. I think reflection make
- the code
[
https://issues.apache.org/jira/browse/SOLR-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015005#comment-16015005
]
Tomás Fernández Löbbe commented on SOLR-9440:
-
I hit this problem all the time in the tests of
[
https://issues.apache.org/jira/browse/SOLR-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya closed SOLR-8440.
--
Resolution: Fixed
> Script support for enabling basic auth
>
[
https://issues.apache.org/jira/browse/SOLR-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya resolved SOLR-10447.
-
Resolution: Fixed
Fix Version/s: master (7.0)
6.6
> An
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-master/1303/
1 tests failed.
FAILED:
org.apache.solr.handler.TestReplicationHandler.doTestReplicateAfterCoreReload
Error Message:
expected:<[{indexVersion=1495060768577,generation=2,filelist=[_bt.cfe, _bt.cfs,
_bt.si, _c4.cfe,
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014937#comment-16014937
]
Vivek Narang edited comment on SOLR-10317 at 5/17/17 11:38 PM:
---
Hi
David, what do you mean by
> Hopefully without generating comments that trigger email/watcher
notifications and thus no more dev list traffic.
How else other than a comment could the system communicate results back to
the user? Or do you mean that whatever runs should post a comment, but
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014937#comment-16014937
]
Vivek Narang commented on SOLR-10317:
-
Hi [~ichattopadhyaya], A quick update. Please access
[
https://issues.apache.org/jira/browse/SOLR-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rong Chen updated SOLR-10702:
-
Description:
similar situation to SOLR-5064, woodstox api has artifact id change from
woodstox-core-asl
[
https://issues.apache.org/jira/browse/SOLR-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rong Chen updated SOLR-10702:
-
Description:
similar situation to SOLR-5064, woodstox api has artifact id change from
woodstox-core-asl
[
https://issues.apache.org/jira/browse/SOLR-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014895#comment-16014895
]
Tomás Fernández Löbbe commented on SOLR-9835:
-
[~caomanhdat], I have a nocommit in SOLR-10233
Rong Chen created SOLR-10702:
Summary: Woodstox API
Key: SOLR-10702
URL: https://issues.apache.org/jira/browse/SOLR-10702
Project: Solr
Issue Type: Bug
Security Level: Public (Default
[
https://issues.apache.org/jira/browse/SOLR-10612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-10612:
Attachment: SOLR-10612.patch
bq. So for example: ... each of the 2 big sections could have "In this
[
https://issues.apache.org/jira/browse/SOLR-10700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-10700:
Attachment: SOLR_10700_Stop_using_PostingsHighlighter.patch
Pretty simple patch. Logs a warning on
[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
Description:
The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
The approach
Mikhail Khludnev created LUCENE-7835:
Summary: ToChildBlockJoinFieldComparator to sort children by a
parent field
Key: LUCENE-7835
URL: https://issues.apache.org/jira/browse/LUCENE-7835
Mikhail Khludnev created SOLR-10701:
---
Summary: sort=parentfield(name,{!child}) asc
Key: SOLR-10701
URL: https://issues.apache.org/jira/browse/SOLR-10701
Project: Solr
Issue Type: New
David Smiley created SOLR-10700:
---
Summary: In 7.0 stop using the PostingsHighlighter
Key: SOLR-10700
URL: https://issues.apache.org/jira/browse/SOLR-10700
Project: Solr
Issue Type: Task
[
https://issues.apache.org/jira/browse/LUCENE-7815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-7815:
-
Attachment: LUCENE_7815_Remove_PostingsHighlighter.patch
The attached patch does what I said. I
[
https://issues.apache.org/jira/browse/SOLR-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014709#comment-16014709
]
David Smiley commented on SOLR-10290:
-
Can we auto-linewrap the asciidoc content we've imported
[
https://issues.apache.org/jira/browse/SOLR-10612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-10612:
Attachment: SOLR-10612.patch
bq. But, maybe there is some stuff we could do with JS and/or the liquid
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014663#comment-16014663
]
Vivek Narang commented on SOLR-10317:
-
Hi [~ab], Thank you for writing this awesome Metrics API. My
[
https://issues.apache.org/jira/browse/SOLR-8847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014628#comment-16014628
]
Yury Kats edited comment on SOLR-8847 at 5/17/17 6:59 PM:
--
"SELECT *" still does
Not sure
1> whether these behaviors are unexpected
2> whether it's in Lucene or Solr
Trying to get my arms around searching times on tlong fields where
docValues=true, indexed=false. I see two behaviors:
behavior 1
multiValued=true or false doesn't matter.
This query:
[
https://issues.apache.org/jira/browse/SOLR-8847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014628#comment-16014628
]
Yury Kats commented on SOLR-8847:
-
"SELECT *" still does not work for queries without a LIMIT, even when
[
https://issues.apache.org/jira/browse/SOLR-10594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev reassigned SOLR-10594:
---
Assignee: Mikhail Khludnev
> Revise SolrConfigHandler.reloadLock after
[
https://issues.apache.org/jira/browse/LUCENE-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014622#comment-16014622
]
David Smiley commented on LUCENE-7834:
--
bq. I am not sure we should do this lazily, it can create a
[
https://issues.apache.org/jira/browse/LUCENE-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014608#comment-16014608
]
Robert Muir commented on LUCENE-7834:
-
I am not sure we should do this lazily, it can create a false
[
https://issues.apache.org/jira/browse/SOLR-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10623:
--
Attachment: SOLR-10623.patch
> Add sql Streaming Expression
>
>
>
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014569#comment-16014569
]
Ishan Chattopadhyaya commented on SOLR-10317:
-
bq. Thanks Ishan Chattopadhyaya This API is
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014542#comment-16014542
]
Vivek Narang commented on SOLR-10317:
-
Thanks [~ichattopadhyaya] This API is Awesome
> Solr
[
https://issues.apache.org/jira/browse/LUCENE-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-7834:
-
Attachment: LUCENE_7834_BlockTreeLazyFST.patch
Attached patch. indexIn is kept open instead of
David Smiley created LUCENE-7834:
Summary: BlockTree's terms index should be loaded into memory
lazily
Key: LUCENE-7834
URL: https://issues.apache.org/jira/browse/LUCENE-7834
Project: Lucene - Core
> Something strange with the links in this message. They refer to both
6.6.0 and 6.5.0 ?
It seems my copy paste of Joel's 6.5 announcement mail didn't affect the
hyperlink, just pasted the text. I wish GMail was smarter. Here's the
correct contents again:
Please vote for release candidate 1
The smoke tester ended with:
SUCCESS! [0:59:34.797969]
However, after looking at some of its output, I see a:
***WARNING***: javadocs want to fail!
Which followed many "missing: ..." messages akin to this:
unpack solr-6.6.0-src.tgz...
make sure no JARs/WARs in src dist...
run
On Wed, 17 May 2017, Ishan Chattopadhyaya wrote:
Please vote for release candidate 1 for Lucene/Solr 6.6.0
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.6.0-RC1-rev4d055f00bba9a745737e4b6c3f9dff06dd35aa2e
> Additionally, we could use that to start running precommit checks on
Jenkins whenever a new patch is put up.
This is a good idea, but we don't want to do this for every patch I'd say.
We encourage people to submit patches early, probably with failing tests
and nocommits. We probably want an
[
https://issues.apache.org/jira/browse/SOLR-7987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014436#comment-16014436
]
Russell Black commented on SOLR-7987:
-
I've submitted a patch for this issue in the related ticket
[
https://issues.apache.org/jira/browse/LUCENE-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernhard Altendorfer updated LUCENE-7833:
-
Summary: Calculating minimum score instead of maximum score in
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014429#comment-16014429
]
Ishan Chattopadhyaya commented on SOLR-10317:
-
You should use the Metrics API
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014418#comment-16014418
]
Vivek Narang commented on SOLR-10317:
-
Hi [~ichattopadhyaya] I am working on making these changes. For
Bernhard Altendorfer created LUCENE-7833:
Summary: Returning minimum instead of maximum in
ToParentBlockJoinQuery.BlockJoinScorer.setScoreAndFreq
Key: LUCENE-7833
URL:
[
https://issues.apache.org/jira/browse/SOLR-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014372#comment-16014372
]
Mark Miller commented on SOLR-10307:
Yeah, these days, the startup scripts are the legit way to start
[
https://issues.apache.org/jira/browse/SOLR-10692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett updated SOLR-10692:
-
Attachment: solr-10692.patch
The attached patch pulls the details of each expression in
[
https://issues.apache.org/jira/browse/SOLR-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Russell Black updated SOLR-9882:
Attachment: SOLR-9882-7987.patch
I have extended Yonik Seeley's patch in this ticket to address the
[
https://issues.apache.org/jira/browse/SOLR-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014345#comment-16014345
]
Mark Miller commented on SOLR-10307:
Ah, sorry, missed that after the break. Yeah, probably at least
[
https://issues.apache.org/jira/browse/SOLR-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014295#comment-16014295
]
Mano Kovacs commented on SOLR-10307:
Thanks, [~markrmil...@gmail.com].
I see you backported to 6x too.
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-10651:
--
Description:
This is a ticket for organizing the new statistical programming features of
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014142#comment-16014142
]
Ishan Chattopadhyaya edited comment on SOLR-10317 at 5/17/17 2:57 PM:
--
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014142#comment-16014142
]
Ishan Chattopadhyaya edited comment on SOLR-10317 at 5/17/17 2:56 PM:
--
For some reason, the artifacts didn't have the Lucene's .asc files copied
over from the working directory to the artifact directory. The Solr ones
were there. I copied them manually, and the smoke tester was happy again.
I'll look into it as to why that could've happened. The raw logs
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014142#comment-16014142
]
Ishan Chattopadhyaya commented on SOLR-10317:
-
bq. The other part of test metadata is test
[
https://issues.apache.org/jira/browse/SOLR-10612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett updated SOLR-10612:
-
Attachment: solr-10612-largepage.patch
I've attached a patch that introduces a new layout
[
https://issues.apache.org/jira/browse/LUCENE-7810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014103#comment-16014103
]
Martijn van Groningen commented on LUCENE-7810:
---
> If we want to be able te reuse cache
Please vote for release candidate 1 for Lucene/Solr 6.6.0
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.6.0-RC1-rev4d055f00bba9a745737e4b6c3f9dff06dd35aa2e
It is open-source, you could just copy the component, compile it
against your version of Solr and load it as an extra library. I don't
think URP interface changed all that much (if at all) in between the
versions.
Regards,
Alex.
http://www.solr-start.com/ - Resources for Solr users, new
[
https://issues.apache.org/jira/browse/LUCENE-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pablo Pita Leira updated LUCENE-7832:
-
Attachment: LUCENE-7832.patch
> atFirstInCurrentDoc is already initialized in base class
Pablo Pita Leira created LUCENE-7832:
Summary: atFirstInCurrentDoc is already initialized in base class
Key: LUCENE-7832
URL: https://issues.apache.org/jira/browse/LUCENE-7832
Project: Lucene -
[
https://issues.apache.org/jira/browse/LUCENE-7778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013958#comment-16013958
]
ASF GitHub Bot commented on LUCENE-7778:
Github user spmason closed the pull request at:
Github user spmason closed the pull request at:
https://github.com/apache/lucene-solr/pull/183
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
[
https://issues.apache.org/jira/browse/SOLR-10594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013864#comment-16013864
]
Mikhail Khludnev commented on SOLR-10594:
-
[~noble.paul], I think I can commit next week if there
Oh nice! Didn't realize that's there in 6x (I'm on 5.5.3). Thanks!!
On Wed, May 17, 2017 at 12:40 AM, David Smiley
wrote:
> SkipExistingDocumentsProcessorFactory
>
94 matches
Mail list logo