[jira] [Commented] (SOLR-11598) Export Writer needs to support more than 4 Sort fields - Say 10, ideally it should not be bound at all, but 4 seems to really short sell the StreamRollup capabilities.

[ https://issues.apache.org/jira/browse/SOLR-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551036#comment-16551036 ] Varun Thacker commented on SOLR-11598: -- Final patch! Pre-commit passes. Plan on com

[jira] [Assigned] (SOLR-12477) Return server error(500) for AlreadyClosedException instead of client Errors(400)

[ https://issues.apache.org/jira/browse/SOLR-12477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker reassigned SOLR-12477: Assignee: Varun Thacker > Return server error(500) for AlreadyClosedException instead of c

[jira] [Commented] (SOLR-12477) Return server error(500) for AlreadyClosedException instead of client Errors(400)

[ https://issues.apache.org/jira/browse/SOLR-12477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551101#comment-16551101 ] Varun Thacker commented on SOLR-12477: -- Hi Jeffery, Patch looks good to me! Perhap

[jira] [Commented] (SOLR-12489) Restore collection does not respect user specified replicationFactor

[ https://issues.apache.org/jira/browse/SOLR-12489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551107#comment-16551107 ] Varun Thacker commented on SOLR-12489: -- Thanks Steve! I'll look into it today > Res

[jira] [Commented] (SOLR-11598) Export Writer needs to support more than 4 Sort fields - Say 10, ideally it should not be bound at all, but 4 seems to really short sell the StreamRollup capabilities.

[ https://issues.apache.org/jira/browse/SOLR-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551163#comment-16551163 ] Varun Thacker commented on SOLR-11598: -- Thanks Amrit for the patch and testing,  cat

[jira] [Assigned] (SOLR-12572) Reuse fieldvalues computed while sorting at writing in ExportWriter

[ https://issues.apache.org/jira/browse/SOLR-12572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker reassigned SOLR-12572: Assignee: Varun Thacker > Reuse fieldvalues computed while sorting at writing in ExportWri

[jira] [Commented] (SOLR-9394) CDCR: Exception on target site while using deleteById to delete a document

[ https://issues.apache.org/jira/browse/SOLR-9394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551318#comment-16551318 ] Varun Thacker commented on SOLR-9394: - {quote} as I believe (from jenkins) this has be

[jira] [Commented] (SOLR-12305) Making buffering tlog bounded for faster recovery

[ https://issues.apache.org/jira/browse/SOLR-12305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551804#comment-16551804 ] Varun Thacker commented on SOLR-12305: -- {quote}+ // package private for testing{quot

[jira] [Commented] (SOLR-12489) Restore collection does not respect user specified replicationFactor

[ https://issues.apache.org/jira/browse/SOLR-12489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551817#comment-16551817 ] Varun Thacker commented on SOLR-12489: -- I beasted the patch 500 times and still hit

[jira] [Updated] (SOLR-12477) Return server error(500) for AlreadyClosedException instead of client Errors(400)

[ https://issues.apache.org/jira/browse/SOLR-12477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12477: - Affects Version/s: (was: 7.3.1) (was: master (8.0)) > Return serve

[jira] [Commented] (SOLR-11598) Export Writer needs to support more than 4 Sort fields - Say 10, ideally it should not be bound at all, but 4 seems to really short sell the StreamRollup capabilities.

[ https://issues.apache.org/jira/browse/SOLR-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553291#comment-16553291 ] Varun Thacker commented on SOLR-11598: -- Thanks Steve for pointing it out! Fixed the

[jira] [Commented] (SOLR-12572) Reuse fieldvalues computed while sorting at writing in ExportWriter

[ https://issues.apache.org/jira/browse/SOLR-12572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553539#comment-16553539 ] Varun Thacker commented on SOLR-12572: -- Thanks Amrit for the patch! Few comments 1.

[jira] [Updated] (SOLR-11598) Export Writer needs to support more than 4 Sort fields - Say 10, ideally it should not be bound at all, but 4 seems to really short sell the StreamRollup capabilities.

[ https://issues.apache.org/jira/browse/SOLR-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-11598: - Affects Version/s: (was: 6.6.1) (was: 7.0) > Export Writer needs t

[jira] [Resolved] (SOLR-11598) Export Writer needs to support more than 4 Sort fields - Say 10, ideally it should not be bound at all, but 4 seems to really short sell the StreamRollup capabilities.

[ https://issues.apache.org/jira/browse/SOLR-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker resolved SOLR-11598. -- Resolution: Fixed Fix Version/s: 7.5 master (8.0) > Export Writer nee

[jira] [Created] (SOLR-12587) Reuse Lucene's PriorityQueue for the ExportHandler

Varun Thacker created SOLR-12587: Summary: Reuse Lucene's PriorityQueue for the ExportHandler Key: SOLR-12587 URL: https://issues.apache.org/jira/browse/SOLR-12587 Project: Solr Issue Type: I

[jira] [Commented] (SOLR-11598) Export Writer needs to support more than 4 Sort fields - Say 10, ideally it should not be bound at all, but 4 seems to really short sell the StreamRollup capabilities.

[ https://issues.apache.org/jira/browse/SOLR-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554654#comment-16554654 ] Varun Thacker commented on SOLR-11598: -- Ughh. Sorry for that Hoss!  I had found tha

[jira] [Commented] (SOLR-12587) Reuse Lucene's PriorityQueue for the ExportHandler

[ https://issues.apache.org/jira/browse/SOLR-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554688#comment-16554688 ] Varun Thacker commented on SOLR-12587: -- Hi [~joel.bernstein] I'm trying to understa

[jira] [Commented] (SOLR-11598) Export Writer needs to support more than 4 Sort fields - Say 10, ideally it should not be bound at all, but 4 seems to really short sell the StreamRollup capabilities.

[ https://issues.apache.org/jira/browse/SOLR-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554705#comment-16554705 ] Varun Thacker commented on SOLR-11598: -- I found another reproducible test failure wh

[jira] [Commented] (SOLR-12587) Reuse Lucene's PriorityQueue for the ExportHandler

[ https://issues.apache.org/jira/browse/SOLR-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554746#comment-16554746 ] Varun Thacker commented on SOLR-12587: -- Here's a version of [SortQueue|[http://exam

[jira] [Comment Edited] (SOLR-12587) Reuse Lucene's PriorityQueue for the ExportHandler

[ https://issues.apache.org/jira/browse/SOLR-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554746#comment-16554746 ] Varun Thacker edited comment on SOLR-12587 at 7/24/18 8:16 PM:

[jira] [Updated] (SOLR-12587) Reuse Lucene's PriorityQueue for the ExportHandler

[ https://issues.apache.org/jira/browse/SOLR-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12587: - Attachment: SOLR-12587.patch > Reuse Lucene's PriorityQueue for the ExportHandler > -

[jira] [Commented] (SOLR-12587) Reuse Lucene's PriorityQueue for the ExportHandler

[ https://issues.apache.org/jira/browse/SOLR-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554890#comment-16554890 ] Varun Thacker commented on SOLR-12587: -- I've put out a patch which is just exploring

[jira] [Commented] (SOLR-12477) Return server error(500) for AlreadyClosedException instead of client Errors(400)

[ https://issues.apache.org/jira/browse/SOLR-12477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555191#comment-16555191 ] Varun Thacker commented on SOLR-12477: -- {quote}- corruptLeader may throw RemoteSolrE

[jira] [Updated] (SOLR-12587) Reuse Lucene's PriorityQueue for the ExportHandler

[ https://issues.apache.org/jira/browse/SOLR-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12587: - Labels: export-writer (was: ) > Reuse Lucene's PriorityQueue for the ExportHandler > ---

[jira] [Commented] (SOLR-12587) Reuse Lucene's PriorityQueue for the ExportHandler

[ https://issues.apache.org/jira/browse/SOLR-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555979#comment-16555979 ] Varun Thacker commented on SOLR-12587: -- Hi Adrien, I thought about that approach in

[jira] [Updated] (SOLR-12542) Trying to export on a non doc-values field gives no response

[ https://issues.apache.org/jira/browse/SOLR-12542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12542: - Labels: export-writer (was: ) > Trying to export on a non doc-values field gives no response > -

[jira] [Updated] (SOLR-12543) Export Handler errors come back with HTTP 200

[ https://issues.apache.org/jira/browse/SOLR-12543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12543: - Labels: export-writer (was: ) > Export Handler errors come back with HTTP 200 >

[jira] [Commented] (SOLR-12587) Reuse Lucene's PriorityQueue for the ExportHandler

[ https://issues.apache.org/jira/browse/SOLR-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556970#comment-16556970 ] Varun Thacker commented on SOLR-12587: -- Thanks Adrien! I worked on a prototype patch

[jira] [Commented] (LUCENE-8428) Allow configurable sentinels in PriorityQueue

[ https://issues.apache.org/jira/browse/LUCENE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558546#comment-16558546 ] Varun Thacker commented on LUCENE-8428: --- +1. LGTM > Allow configurable sentinels

[jira] [Commented] (SOLR-9471) Another race condition in ClusterStatus.getClusterStatus

[ https://issues.apache.org/jira/browse/SOLR-9471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539171#comment-16539171 ] Varun Thacker commented on SOLR-9471: - Hi [~alexey] / [~shalinmangar]  Can we close o

[jira] [Commented] (SOLR-10720) Aggressive removal of a collection breaks cluster state

[ https://issues.apache.org/jira/browse/SOLR-10720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539179#comment-16539179 ] Varun Thacker commented on SOLR-10720: -- {code:java} } catch (SolrException e) { if

[jira] [Commented] (SOLR-10720) Aggressive removal of a collection breaks cluster state

[ https://issues.apache.org/jira/browse/SOLR-10720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539182#comment-16539182 ] Varun Thacker commented on SOLR-10720: -- Okay so the user was HttpClusterStateProvide

[jira] [Updated] (SOLR-12542) Trying to export on a non doc-values field gives no response

[ https://issues.apache.org/jira/browse/SOLR-12542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12542: - Attachment: chrome.png > Trying to export on a non doc-values field gives no response > -

[jira] [Created] (SOLR-12542) Trying to export on a non doc-values field gives no response

Varun Thacker created SOLR-12542: Summary: Trying to export on a non doc-values field gives no response Key: SOLR-12542 URL: https://issues.apache.org/jira/browse/SOLR-12542 Project: Solr Is

[jira] [Updated] (SOLR-12543) Export Handler errors come back with HTTP 200

[ https://issues.apache.org/jira/browse/SOLR-12543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12543: - Description: If I do a wrong export query like this we get back http code 200 {code:java} ~/solr-

[jira] [Created] (SOLR-12543) Export Handler errors come back with HTTP 200

Varun Thacker created SOLR-12543: Summary: Export Handler errors come back with HTTP 200 Key: SOLR-12543 URL: https://issues.apache.org/jira/browse/SOLR-12543 Project: Solr Issue Type: Bug

[jira] [Commented] (SOLR-12412) Leader should give up leadership when IndexWriter.tragedy occur

[ https://issues.apache.org/jira/browse/SOLR-12412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539268#comment-16539268 ] Varun Thacker commented on SOLR-12412: -- Hi [~caomanhdat] ,   Maybe we could do som

[jira] [Created] (SOLR-12544) ZkStateReader can cache deleted collections and never refresh it

Varun Thacker created SOLR-12544: Summary: ZkStateReader can cache deleted collections and never refresh it Key: SOLR-12544 URL: https://issues.apache.org/jira/browse/SOLR-12544 Project: Solr

[jira] [Updated] (SOLR-12544) ZkStateReader can cache deleted collections and never refresh it

[ https://issues.apache.org/jira/browse/SOLR-12544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12544: - Attachment: (was: SOLR-12544_Solr721.patch) > ZkStateReader can cache deleted collections and

[jira] [Updated] (SOLR-12544) ZkStateReader can cache deleted collections and never refresh it

[ https://issues.apache.org/jira/browse/SOLR-12544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12544: - Attachment: SOLR-12544_Solr721.patch > ZkStateReader can cache deleted collections and never refr

[jira] [Updated] (SOLR-11598) Export Writer needs to support more than 4 Sort fields - Say 10, ideally it should not be bound at all, but 4 seems to really short sell the StreamRollup capabilities.

[ https://issues.apache.org/jira/browse/SOLR-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-11598: - Attachment: SOLR-11598.patch > Export Writer needs to support more than 4 Sort fields - Say 10, i

[jira] [Commented] (SOLR-11598) Export Writer needs to support more than 4 Sort fields - Say 10, ideally it should not be bound at all, but 4 seems to really short sell the StreamRollup capabilities.

[ https://issues.apache.org/jira/browse/SOLR-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543791#comment-16543791 ] Varun Thacker commented on SOLR-11598: -- Patch which builds on top of Amrit's patch

[jira] [Commented] (SOLR-12713) make "solr.data.dir" points to multiple base path, and collection's replicas may distribute in them

[ https://issues.apache.org/jira/browse/SOLR-12713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599547#comment-16599547 ] Varun Thacker commented on SOLR-12713: -- {quote}be my pleasure to implement this if p

[jira] [Commented] (SOLR-12704) NPE in AddSchemaFieldsUpdateProcessorFactory

[ https://issues.apache.org/jira/browse/SOLR-12704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599550#comment-16599550 ] Varun Thacker commented on SOLR-12704: -- Thanks Steve! > NPE in AddSchemaFieldsUpdat

[jira] [Updated] (SOLR-10697) Improve defaults for maxConnectionsPerHost

[ https://issues.apache.org/jira/browse/SOLR-10697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-10697: - Fix Version/s: 7.5 master (8.0) > Improve defaults for maxConnectionsPerHost >

[jira] [Created] (SOLR-12734) Don't capture certain admin handler metrics

Varun Thacker created SOLR-12734: Summary: Don't capture certain admin handler metrics Key: SOLR-12734 URL: https://issues.apache.org/jira/browse/SOLR-12734 Project: Solr Issue Type: Improvem

[jira] [Updated] (SOLR-12734) Don't capture metrics for certain admin handlers

[ https://issues.apache.org/jira/browse/SOLR-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12734: - Summary: Don't capture metrics for certain admin handlers (was: Don't capture certain admin hand

[jira] [Created] (SOLR-12735) Metrics History always shows NaN for numNodes

Varun Thacker created SOLR-12735: Summary: Metrics History always shows NaN for numNodes Key: SOLR-12735 URL: https://issues.apache.org/jira/browse/SOLR-12735 Project: Solr Issue Type: Improv

[jira] [Resolved] (SOLR-12653) Metrics History doesn't work when the system collection is enabled

[ https://issues.apache.org/jira/browse/SOLR-12653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker resolved SOLR-12653. -- Resolution: Won't Fix Tried it on master right now and it works for me. So even if this was a b

[jira] [Commented] (SOLR-12734) Don't capture metrics for certain admin handlers

[ https://issues.apache.org/jira/browse/SOLR-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603871#comment-16603871 ] Varun Thacker commented on SOLR-12734: --   {quote}No matter what, we disable some and

[jira] [Resolved] (SOLR-12599) Add search routing documentation

[ https://issues.apache.org/jira/browse/SOLR-12599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker resolved SOLR-12599. -- Resolution: Fixed Fix Version/s: 7.5 master (8.0) > Add search routin

[jira] [Updated] (SOLR-12457) field(x,min|max) sorting doesn't work on trie or str fields in multi-shard collections

[ https://issues.apache.org/jira/browse/SOLR-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12457: - Labels: trie (was: ) > field(x,min|max) sorting doesn't work on trie or str fields in multi-shar

[jira] [Updated] (SOLR-12457) field(x,min|max) sorting doesn't work on trie or str fields in multi-shard collections

[ https://issues.apache.org/jira/browse/SOLR-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12457: - Labels: numeric-tries-to-points (was: trie) > field(x,min|max) sorting doesn't work on trie or s

[jira] [Created] (SOLR-12744) A high numRecordsToKeep can flood the info log message printing all the versions

Varun Thacker created SOLR-12744: Summary: A high numRecordsToKeep can flood the info log message printing all the versions Key: SOLR-12744 URL: https://issues.apache.org/jira/browse/SOLR-12744 Projec

[jira] [Commented] (SOLR-12744) A high numRecordsToKeep can flood the info log message printing all the versions

[ https://issues.apache.org/jira/browse/SOLR-12744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604824#comment-16604824 ] Varun Thacker commented on SOLR-12744: -- There are a couple of other log entries from

[jira] [Updated] (SOLR-12744) A high numRecordsToKeep can flood the info log message printing all the versions

[ https://issues.apache.org/jira/browse/SOLR-12744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12744: - Attachment: SOLR-12744.patch > A high numRecordsToKeep can flood the info log message printing al

[jira] [Commented] (SOLR-12744) A high numRecordsToKeep can flood the info log message printing all the versions

[ https://issues.apache.org/jira/browse/SOLR-12744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605178#comment-16605178 ] Varun Thacker commented on SOLR-12744: -- good idea! Let me update the patch in a minu

[jira] [Updated] (SOLR-12744) A high numRecordsToKeep can flood the info log message printing all the versions

[ https://issues.apache.org/jira/browse/SOLR-12744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12744: - Attachment: SOLR-12744.patch > A high numRecordsToKeep can flood the info log message printing al

[jira] [Commented] (SOLR-12744) A high numRecordsToKeep can flood the info log message printing all the versions

[ https://issues.apache.org/jira/browse/SOLR-12744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605181#comment-16605181 ] Varun Thacker commented on SOLR-12744: -- {code:java} [master] ~/apache-work/lucene-so

[jira] [Commented] (SOLR-12744) A high numRecordsToKeep can flood the info log message printing all the versions

[ https://issues.apache.org/jira/browse/SOLR-12744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605188#comment-16605188 ] Varun Thacker commented on SOLR-12744: -- Thanks Dat! I'll commit this shortly. When I

[jira] [Updated] (SOLR-12744) A high numRecordsToKeep can flood the info log message printing all the versions

[ https://issues.apache.org/jira/browse/SOLR-12744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12744: - Attachment: SOLR-12744.patch > A high numRecordsToKeep can flood the info log message printing al

[jira] [Updated] (SOLR-12744) Improve logging message and verbosity around recoveries

[ https://issues.apache.org/jira/browse/SOLR-12744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12744: - Summary: Improve logging message and verbosity around recoveries (was: A high numRecordsToKeep c

[jira] [Resolved] (SOLR-12744) Improve logging message and verbosity around recoveries

[ https://issues.apache.org/jira/browse/SOLR-12744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker resolved SOLR-12744. -- Resolution: Fixed Fix Version/s: 7.5 master (8.0) Thanks Dat! > Impr

[jira] [Commented] (SOLR-10697) Improve defaults for maxConnectionsPerHost

[ https://issues.apache.org/jira/browse/SOLR-10697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606225#comment-16606225 ] Varun Thacker commented on SOLR-10697: -- Thanks Cassandra! I didn't occur to me that

[jira] [Commented] (SOLR-9786) Defer creation of clauses in parser, optionally delegate groups to FieldType.getSetQuery

[ https://issues.apache.org/jira/browse/SOLR-9786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607716#comment-16607716 ] Varun Thacker commented on SOLR-9786: - I was trying to find this Jira to see what vers

[jira] [Commented] (SOLR-11836) Use -1 in bucketSizeLimit to get all facets, analogous to the JSON facet API

[ https://issues.apache.org/jira/browse/SOLR-11836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611004#comment-16611004 ] Varun Thacker commented on SOLR-11836: -- Patch applies cleanly on master. Looks good

[jira] [Commented] (SOLR-11836) Use -1 in bucketSizeLimit to get all facets, analogous to the JSON facet API

[ https://issues.apache.org/jira/browse/SOLR-11836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611011#comment-16611011 ] Varun Thacker commented on SOLR-11836: -- Running tests and committing it to master an

[jira] [Updated] (SOLR-13288) Async logging max length should only apply to the message

[ https://issues.apache.org/jira/browse/SOLR-13288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-13288: - Description: After SOLR-12753 messages are limited to 10240 chars. +1 for having a limit, we eve

[jira] [Created] (SOLR-13288) Async logging max length should only apply to the message

Varun Thacker created SOLR-13288: Summary: Async logging max length should only apply to the message Key: SOLR-13288 URL: https://issues.apache.org/jira/browse/SOLR-13288 Project: Solr Issue

[jira] [Commented] (SOLR-9952) S3BackupRepository

[ https://issues.apache.org/jira/browse/SOLR-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852425#comment-16852425 ] Varun Thacker commented on SOLR-9952: - Here is what I tried on Solr 8.1.1 and the erro

[jira] [Comment Edited] (SOLR-9952) S3BackupRepository

[ https://issues.apache.org/jira/browse/SOLR-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852425#comment-16852425 ] Varun Thacker edited comment on SOLR-9952 at 5/30/19 11:39 PM: -

[jira] [Comment Edited] (SOLR-9952) S3BackupRepository

[ https://issues.apache.org/jira/browse/SOLR-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852425#comment-16852425 ] Varun Thacker edited comment on SOLR-9952 at 5/30/19 11:39 PM: -

[jira] [Comment Edited] (SOLR-9952) S3BackupRepository

[ https://issues.apache.org/jira/browse/SOLR-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852425#comment-16852425 ] Varun Thacker edited comment on SOLR-9952 at 5/30/19 11:40 PM: -

[jira] [Commented] (SOLR-9952) S3BackupRepository

[ https://issues.apache.org/jira/browse/SOLR-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852465#comment-16852465 ] Varun Thacker commented on SOLR-9952: - So the only namespace conflict for a user runni

[jira] [Commented] (SOLR-9952) S3BackupRepository

[ https://issues.apache.org/jira/browse/SOLR-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853404#comment-16853404 ] Varun Thacker commented on SOLR-9952: - {quote}Ok let me take my statement back. The pr

[jira] [Commented] (SOLR-13533) Code Cleanup - Performance

[ https://issues.apache.org/jira/browse/SOLR-13533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859503#comment-16859503 ] Varun Thacker commented on SOLR-13533: -- Hi Kevin, Splitting them up will always be

[jira] [Commented] (SOLR-13533) Code Cleanup - Performance

[ https://issues.apache.org/jira/browse/SOLR-13533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859687#comment-16859687 ] Varun Thacker commented on SOLR-13533: -- {quote}bq.  The name's "Koen" by the way :P

[jira] [Commented] (LUCENE-8847) Code Cleanup: Rewrite StringBuilder.append with concatted strings

[ https://issues.apache.org/jira/browse/LUCENE-8847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16860130#comment-16860130 ] Varun Thacker commented on LUCENE-8847: --- Thanks Uwe! > Code Cleanup: Rewrite Stri

[jira] [Resolved] (SOLR-12488) Rewrite exists field value query to leverage DocValuesFieldExistsQuery and NormsFieldExistsQuery

[ https://issues.apache.org/jira/browse/SOLR-12488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker resolved SOLR-12488. -- Resolution: Duplicate Indeed! I'll close this one out. > Rewrite exists field value query to l

[jira] [Commented] (SOLR-13452) Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.

[ https://issues.apache.org/jira/browse/SOLR-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845411#comment-16845411 ] Varun Thacker commented on SOLR-13452: -- When i run {{./gradlew runjflex}} this the S

[jira] [Comment Edited] (SOLR-13452) Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.

[ https://issues.apache.org/jira/browse/SOLR-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845411#comment-16845411 ] Varun Thacker edited comment on SOLR-13452 at 5/22/19 1:31 AM:

[jira] [Comment Edited] (SOLR-13452) Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.

[ https://issues.apache.org/jira/browse/SOLR-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845411#comment-16845411 ] Varun Thacker edited comment on SOLR-13452 at 5/22/19 1:39 AM:

[jira] [Created] (SOLR-12673) Union Has All Post Filter Query

Varun Thacker created SOLR-12673: Summary: Union Has All Post Filter Query Key: SOLR-12673 URL: https://issues.apache.org/jira/browse/SOLR-12673 Project: Solr Issue Type: New Feature Se

[jira] [Commented] (SOLR-12405) Add a quality of service type filter for request load management and request throttling.

[ https://issues.apache.org/jira/browse/SOLR-12405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583038#comment-16583038 ] Varun Thacker commented on SOLR-12405: -- Here's an interesting article for reference

[jira] [Created] (SOLR-12674) RollupStream should not use the HashQueryParser for 1 worker

Varun Thacker created SOLR-12674: Summary: RollupStream should not use the HashQueryParser for 1 worker Key: SOLR-12674 URL: https://issues.apache.org/jira/browse/SOLR-12674 Project: Solr Is

[jira] [Updated] (SOLR-12673) Superset Query

[ https://issues.apache.org/jira/browse/SOLR-12673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12673: - Summary: Superset Query (was: Union Has All Post Filter Query) > Superset Query > --

[jira] [Commented] (SOLR-12673) Superset Query

[ https://issues.apache.org/jira/browse/SOLR-12673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583217#comment-16583217 ] Varun Thacker commented on SOLR-12673: -- After some offline discussion with Steve a s

[jira] [Commented] (SOLR-12672) Implement Synchronized Disruption into Solr

[ https://issues.apache.org/jira/browse/SOLR-12672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584832#comment-16584832 ] Varun Thacker commented on SOLR-12672: -- {quote}By implementing a synchronized disrup

[jira] [Updated] (SOLR-12674) RollupStream should not use the HashQueryParser for 1 worker

[ https://issues.apache.org/jira/browse/SOLR-12674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-12674: - Attachment: SOLR-12674.patch > RollupStream should not use the HashQueryParser for 1 worker > ---

[jira] [Commented] (SOLR-12674) RollupStream should not use the HashQueryParser for 1 worker

[ https://issues.apache.org/jira/browse/SOLR-12674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585170#comment-16585170 ] Varun Thacker commented on SOLR-12674: -- After this patch the hash query parser is on

[jira] [Resolved] (SOLR-12624) Better validation for HashQParserPlugin

[ https://issues.apache.org/jira/browse/SOLR-12624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker resolved SOLR-12624. -- Resolution: Duplicate > Better validation for HashQParserPlugin > -

[jira] [Commented] (SOLR-12624) Better validation for HashQParserPlugin

[ https://issues.apache.org/jira/browse/SOLR-12624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585172#comment-16585172 ] Varun Thacker commented on SOLR-12624: -- This will be addressed as part of SOLR-12674

[jira] [Resolved] (SOLR-12674) RollupStream should not use the HashQueryParser for 1 worker

[ https://issues.apache.org/jira/browse/SOLR-12674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker resolved SOLR-12674. -- Resolution: Fixed Fix Version/s: 7.5 > RollupStream should not use the HashQueryParser f

[jira] [Commented] (SOLR-12587) Reuse Lucene's PriorityQueue for the ExportHandler

[ https://issues.apache.org/jira/browse/SOLR-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585428#comment-16585428 ] Varun Thacker commented on SOLR-12587: -- When I took a deeper look at it today there

[jira] [Commented] (SOLR-12673) Superset Query

[ https://issues.apache.org/jira/browse/SOLR-12673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586377#comment-16586377 ] Varun Thacker commented on SOLR-12673: -- Thanks everyone for the tips! Here's a ind

[jira] [Comment Edited] (SOLR-12673) Superset Query

[ https://issues.apache.org/jira/browse/SOLR-12673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586377#comment-16586377 ] Varun Thacker edited comment on SOLR-12673 at 8/20/18 7:13 PM:

[jira] [Updated] (SOLR-11598) ExportWriter should support sorting on more than 4 sort fields

[ https://issues.apache.org/jira/browse/SOLR-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-11598: - Summary: ExportWriter should support sorting on more than 4 sort fields (was: Export Writer need

[jira] [Resolved] (SOLR-12635) HashQParserPlugin should be run as a post filter cost is not explicitly defined

[ https://issues.apache.org/jira/browse/SOLR-12635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker resolved SOLR-12635. -- Resolution: Won't Fix > HashQParserPlugin should be run as a post filter cost is not explicitly

[jira] [Commented] (SOLR-12635) HashQParserPlugin should be run as a post filter cost is not explicitly defined

[ https://issues.apache.org/jira/browse/SOLR-12635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586536#comment-16586536 ] Varun Thacker commented on SOLR-12635: -- There was a concern that if you do rollups o

[jira] [Commented] (SOLR-12635) HashQParserPlugin should be run as a post filter cost is not explicitly defined

[ https://issues.apache.org/jira/browse/SOLR-12635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586546#comment-16586546 ] Varun Thacker commented on SOLR-12635: -- {quote}Infact if you provide more than 4 par

<    1   2   3   4   5   6   7   8   9   10   >