[jira] [Updated] (SOLR-10406) v2 API error messages list the URL request path as /solr/____v2/... when the original path was /v2/...

[ https://issues.apache.org/jira/browse/SOLR-10406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10406: Attachment: SOLR-10406.patch Updated patch for this ticket. With this patch - when request v2 api

[jira] [Commented] (SOLR-10715) /v2/ should not be an alias for /v2/collections

[ https://issues.apache.org/jira/browse/SOLR-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039371#comment-16039371 ] Cao Manh Dat commented on SOLR-10715: - Oh, ok. So [~ctargett] do you think that above response will

[jira] [Comment Edited] (SOLR-10715) /v2/ should not be an alias for /v2/collections

[ https://issues.apache.org/jira/browse/SOLR-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038666#comment-16038666 ] Cao Manh Dat edited comment on SOLR-10715 at 6/6/17 11:37 AM: -- [~janhoy]

[jira] [Commented] (SOLR-10715) /v2/ should not be an alias for /v2/collections

[ https://issues.apache.org/jira/browse/SOLR-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038666#comment-16038666 ] Cao Manh Dat commented on SOLR-10715: - [~janhoy] {{_introspect}} is documentation page for correspond

[jira] [Updated] (SOLR-8256) Set legacyCloud=false as default

[ https://issues.apache.org/jira/browse/SOLR-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-8256: --- Attachment: SOLR-8256.patch Fix an issue when cluster props already exist when run the test. Will

[jira] [Commented] (SOLR-10715) /v2/ should not be an alias for /v2/collections

[ https://issues.apache.org/jira/browse/SOLR-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038131#comment-16038131 ] Cao Manh Dat commented on SOLR-10715: - [~janhoy] Do you think this result returned from {{/v2}} is

[jira] [Closed] (SOLR-10413) v2 API: parsed JSON type should be coerced to expected type

[ https://issues.apache.org/jira/browse/SOLR-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat closed SOLR-10413. --- Resolution: Fixed > v2 API: parsed JSON type should be coerced to expected type >

[jira] [Commented] (SOLR-7251) In legacyCloud=false, If a create collection fails, information about that collection should not be persisted in ZK

[ https://issues.apache.org/jira/browse/SOLR-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038006#comment-16038006 ] Cao Manh Dat commented on SOLR-7251: [~varunthacker] By looking at currently {{CreateCollectionCmd}},

[jira] [Comment Edited] (SOLR-8256) Set legacyCloud=false as default

[ https://issues.apache.org/jira/browse/SOLR-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037917#comment-16037917 ] Cao Manh Dat edited comment on SOLR-8256 at 6/6/17 12:53 AM: - Final patch for

[jira] [Updated] (SOLR-8256) Set legacyCloud=false as default

[ https://issues.apache.org/jira/browse/SOLR-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-8256: --- Attachment: SOLR-8256.patch Final patch for this ticket, in this patch I changed

[jira] [Updated] (SOLR-8256) Set legacyCloud=false as default

[ https://issues.apache.org/jira/browse/SOLR-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-8256: --- Attachment: SOLR-8256.patch Updated patch based on [~varunthacker]'s comments. > Set

[jira] [Comment Edited] (SOLR-8256) Set legacyCloud=false as default

[ https://issues.apache.org/jira/browse/SOLR-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036651#comment-16036651 ] Cao Manh Dat edited comment on SOLR-8256 at 6/5/17 7:59 AM: [~varunthacker] I

[jira] [Commented] (SOLR-8256) Set legacyCloud=false as default

[ https://issues.apache.org/jira/browse/SOLR-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036651#comment-16036651 ] Cao Manh Dat commented on SOLR-8256: [~varunthacker] I did write a test to check for the async of

[jira] [Comment Edited] (SOLR-8256) Set legacyCloud=false as default

[ https://issues.apache.org/jira/browse/SOLR-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036488#comment-16036488 ] Cao Manh Dat edited comment on SOLR-8256 at 6/5/17 3:42 AM: [~varunthacker] for

[jira] [Commented] (SOLR-8256) Set legacyCloud=false as default

[ https://issues.apache.org/jira/browse/SOLR-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036488#comment-16036488 ] Cao Manh Dat commented on SOLR-8256: [~varunthacker] for CreateShardCmd, we will return immediately

[jira] [Commented] (SOLR-8256) Set legacyCloud=false as default

[ https://issues.apache.org/jira/browse/SOLR-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035970#comment-16035970 ] Cao Manh Dat commented on SOLR-8256: I'm wrong, {{ReplaceNodeTest}} also failed in master branch {code}

[jira] [Updated] (SOLR-8256) Set legacyCloud=false as default

[ https://issues.apache.org/jira/browse/SOLR-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-8256: --- Summary: Set legacyCloud=false as default (was: Remove cluster setting 'legacy cloud' in 6x.) > Set

[jira] [Updated] (SOLR-8256) Remove cluster setting 'legacy cloud' in 6x.

[ https://issues.apache.org/jira/browse/SOLR-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-8256: --- Attachment: SOLR-8256.patch Updated patch for this ticket, only {{ReplaceNodeTest}} is still fail. >

[jira] [Updated] (SOLR-8256) Remove cluster setting 'legacy cloud' in 6x.

[ https://issues.apache.org/jira/browse/SOLR-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-8256: --- Attachment: SOLR-8256.patch A patch for this ticket, Some tests still failed, but here is the idea how

[jira] [Comment Edited] (SOLR-10711) Solr V2 API should work on standalone nodes

[ https://issues.apache.org/jira/browse/SOLR-10711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16018303#comment-16018303 ] Cao Manh Dat edited comment on SOLR-10711 at 5/20/17 3:59 AM: -- A patch for

[jira] [Comment Edited] (SOLR-10711) Solr V2 API should work on standalone nodes

[ https://issues.apache.org/jira/browse/SOLR-10711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16018303#comment-16018303 ] Cao Manh Dat edited comment on SOLR-10711 at 5/20/17 3:58 AM: -- A patch for

[jira] [Updated] (SOLR-10711) Solr V2 API should work on standalone nodes

[ https://issues.apache.org/jira/browse/SOLR-10711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10711: Attachment: SOLR-10711.patch A patch for this ticket, so instead of redirect "/v2" ->

[jira] [Commented] (SOLR-10406) v2 API error messages list the URL request path as /solr/____v2/... when the original path was /v2/...

[ https://issues.apache.org/jira/browse/SOLR-10406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017133#comment-16017133 ] Cao Manh Dat commented on SOLR-10406: - Here are result returned by solr with the patch Case 1 : For

[jira] [Updated] (SOLR-10406) v2 API error messages list the URL request path as /solr/____v2/... when the original path was /v2/...

[ https://issues.apache.org/jira/browse/SOLR-10406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10406: Attachment: (was: SOLR-10406.patch) > v2 API error messages list the URL request path as

[jira] [Updated] (SOLR-10406) v2 API error messages list the URL request path as /solr/____v2/... when the original path was /v2/...

[ https://issues.apache.org/jira/browse/SOLR-10406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10406: Attachment: SOLR-10406.patch > v2 API error messages list the URL request path as /solr/v2/...

[jira] [Updated] (SOLR-10406) v2 API error messages list the URL request path as /solr/____v2/... when the original path was /v2/...

[ https://issues.apache.org/jira/browse/SOLR-10406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10406: Attachment: SOLR-10406.patch Patch for this ticket, exceptions are nicely written by response

[jira] [Resolved] (SOLR-10413) v2 API: parsed JSON type should be coerced to expected type

[ https://issues.apache.org/jira/browse/SOLR-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat resolved SOLR-10413. - Resolution: Fixed Assignee: Cao Manh Dat Fix Version/s: master (7.0) > v2 API:

[jira] [Updated] (SOLR-10413) v2 API: parsed JSON type should be coerced to expected type

[ 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

[jira] [Resolved] (SOLR-10434) Create a new mapping for admin calls & non-admin calls in v2 end points

[ 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

[jira] [Commented] (SOLR-10413) v2 API: parsed JSON type should be coerced to expected type

[ 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

[jira] [Commented] (SOLR-10413) v2 API: parsed JSON type should be coerced to expected type

[ 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

[jira] [Comment Edited] (SOLR-10413) v2 API: parsed JSON type should be coerced to expected type

[ https://issues.apache.org/jira/browse/SOLR-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16012415#comment-16012415 ] Cao Manh Dat edited comment on SOLR-10413 at 5/16/17 1:49 PM: -- A patch for

[jira] [Updated] (SOLR-10413) v2 API: parsed JSON type should be coerced to expected type

[ 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 A patch for this ticket, I've rewritten json validator from scratch.

[jira] [Closed] (SOLR-10412) v2 API: many API command specification properties are typed "number" but should instead be typed "integer"

[ https://issues.apache.org/jira/browse/SOLR-10412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat closed SOLR-10412. --- Resolution: Fixed Assignee: Cao Manh Dat Fix Version/s: master (7.0) > v2 API: many

[jira] [Closed] (SOLR-10405) v2 API introspect response contains multiple copies of the experimental format WARNING

[ https://issues.apache.org/jira/browse/SOLR-10405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat closed SOLR-10405. --- Resolution: Fixed Fix Version/s: master (7.0) > v2 API introspect response contains multiple

[jira] [Closed] (SOLR-10411) v2 Collection API "modify" command specification's replicationFactor property is incorrectly typed as string, should be integer

[ https://issues.apache.org/jira/browse/SOLR-10411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat closed SOLR-10411. --- Resolution: Fixed Fix Version/s: master (7.0) > v2 Collection API "modify" command

[jira] [Assigned] (SOLR-10411) v2 Collection API "modify" command specification's replicationFactor property is incorrectly typed as string, should be integer

[ https://issues.apache.org/jira/browse/SOLR-10411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat reassigned SOLR-10411: --- Assignee: Cao Manh Dat > v2 Collection API "modify" command specification's

[jira] [Updated] (SOLR-10405) v2 API introspect response contains multiple copies of the experimental format WARNING

[ https://issues.apache.org/jira/browse/SOLR-10405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10405: Attachment: SOLR-10405.patch A patch for this ticket. > v2 API introspect response contains

[jira] [Closed] (SOLR-10408) v2 API introspect should return useful message for non-existent command

[ https://issues.apache.org/jira/browse/SOLR-10408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat closed SOLR-10408. --- Resolution: Fixed Fix Version/s: master (7.0) > v2 API introspect should return useful message

[jira] [Comment Edited] (SOLR-10408) v2 API introspect should return useful message for non-existent command

[ https://issues.apache.org/jira/browse/SOLR-10408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006042#comment-16006042 ] Cao Manh Dat edited comment on SOLR-10408 at 5/12/17 1:10 AM: -- Trivial patch

[jira] [Updated] (SOLR-10408) v2 API introspect should return useful message for non-existent command

[ https://issues.apache.org/jira/browse/SOLR-10408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10408: Summary: v2 API introspect should return useful message for non-existent command (was: v2 API

[jira] [Assigned] (SOLR-10408) v2 API introspect should fail when filtering for a non-existent command

[ https://issues.apache.org/jira/browse/SOLR-10408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat reassigned SOLR-10408: --- Assignee: Cao Manh Dat > v2 API introspect should fail when filtering for a non-existent

[jira] [Updated] (SOLR-10408) v2 API introspect should fail when filtering for a non-existent command

[ https://issues.apache.org/jira/browse/SOLR-10408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10408: Attachment: SOLR-10408.patch Trivial patch for this ticket. > v2 API introspect should fail when

[jira] [Commented] (SOLR-10431) Make it possible to invoke v2 api calls using SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005824#comment-16005824 ] Cao Manh Dat commented on SOLR-10431: - Thanks [~noble.paul] and [~shalinmangar] > Make it possible to

[jira] [Closed] (SOLR-10431) Make it possible to invoke v2 api calls using SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat closed SOLR-10431. --- Resolution: Fixed Fix Version/s: master (7.0) > Make it possible to invoke v2 api calls using

[jira] [Closed] (SOLR-10619) Optimize using cache for DistributedQueue in case of single-consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat closed SOLR-10619. --- Resolution: Fixed Fix Version/s: master (7.0) 6.6 > Optimize using cache

[jira] [Updated] (SOLR-10524) Better ZkStateWriter batching

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10524: Fix Version/s: master (7.0) 6.6 > Better ZkStateWriter batching >

[jira] [Resolved] (SOLR-10524) Better ZkStateWriter batching

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat resolved SOLR-10524. - Resolution: Fixed > Better ZkStateWriter batching > - > >

[jira] [Assigned] (SOLR-10524) Better ZkStateWriter batching

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat reassigned SOLR-10524: --- Assignee: Cao Manh Dat > Better ZkStateWriter batching > - > >

[jira] [Commented] (SOLR-10619) Optimize using cache for DistributedQueue in case of single-consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002346#comment-16002346 ] Cao Manh Dat commented on SOLR-10619: - Thanks [~dragonsinth] and [~shalinmangar] > Optimize using

[jira] [Updated] (SOLR-10619) Optimize using cache for DistributedQueue in case of single-consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10619: Summary: Optimize using cache for DistributedQueue in case of single-consumer (was: Optimize using

[jira] [Commented] (SOLR-10619) Optimize using cache for DQ.peek(), DQ.poll() in case of single-consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002157#comment-16002157 ] Cao Manh Dat commented on SOLR-10619: - [~dragonsinth] The patch LGTM, I will commit the patch soon. >

[jira] [Updated] (SOLR-10619) Optimize using cache for DQ.peek(), DQ.poll() in case of single-consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10619: Summary: Optimize using cache for DQ.peek(), DQ.poll() in case of single-consumer (was: When

[jira] [Updated] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10619: Attachment: SOLR-10619.patch Introduced a flag to {{firstChild}} so {{peekElements}} can expect the

[jira] [Commented] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001975#comment-16001975 ] Cao Manh Dat commented on SOLR-10619: - The patch make {{MultiThreadedOCPTest.testFillWorkQueue()}}

[jira] [Commented] (SOLR-10524) Better ZkStateWriter batching

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001846#comment-16001846 ] Cao Manh Dat commented on SOLR-10524: - Looks good +1 for commit > Better ZkStateWriter batching >

[jira] [Updated] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10619: Attachment: SOLR-10619.patch Updated patch for this ticket. In this patch, {{firstChild()}} will

[jira] [Issue Comment Deleted] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10619: Comment: was deleted (was: [~dragonsinth] Can you take a look at this patch? Thanks

[jira] [Updated] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10619: Attachment: (was: SOLR-10619.patch) > When DQ.knowChildren is not empty, DQ should not refetch

[jira] [Updated] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10619: Attachment: SOLR-10619.patch [~dragonsinth] Can you take a look at this patch? Thanks

[jira] [Commented] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999654#comment-15999654 ] Cao Manh Dat commented on SOLR-10619: - Yeah, that's the reason why I added a flag ( single-consumer )

[jira] [Commented] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999591#comment-15999591 ] Cao Manh Dat commented on SOLR-10619: - But instead of refetch the child list from ZK when there's no

[jira] [Commented] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999590#comment-15999590 ] Cao Manh Dat commented on SOLR-10619: - bq. I completely follow your logic. But then, why do we need a

[jira] [Commented] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999326#comment-15999326 ] Cao Manh Dat commented on SOLR-10619: - [~dragonsinth] "singleConsumer" ( multiple producer single

[jira] [Updated] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10619: Attachment: SOLR-10619.patch I think this patch is ready to be committed. [~dragonsinth] Can you

[jira] [Updated] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10619: Attachment: SOLR-10619.patch > When DQ.knowChildren is not empty, DQ should not refetch node

[jira] [Updated] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10619: Attachment: (was: SOLR-10619.patch) > When DQ.knowChildren is not empty, DQ should not refetch

[jira] [Comment Edited] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999228#comment-15999228 ] Cao Manh Dat edited comment on SOLR-10619 at 5/6/17 2:31 AM: - Initial patch

[jira] [Updated] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10619: Attachment: SOLR-10619.patch Initial patch for this ticket. The Overseer.testPerformance time

[jira] [Created] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

Cao Manh Dat created SOLR-10619: --- Summary: When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer Key: SOLR-10619 URL: https://issues.apache.org/jira/browse/SOLR-10619

[jira] [Assigned] (SOLR-10619) When DQ.knowChildren is not empty, DQ should not refetch node children in case of single consumer

[ https://issues.apache.org/jira/browse/SOLR-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat reassigned SOLR-10619: --- Assignee: Cao Manh Dat > When DQ.knowChildren is not empty, DQ should not refetch node

[jira] [Commented] (SOLR-10524) Explore in-memory partitioning for processing Overseer queue messages

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999217#comment-15999217 ] Cao Manh Dat commented on SOLR-10524: - I will commit the patch soon if no one have any objection. >

[jira] [Updated] (SOLR-10431) Make it possible to invoke v2 api calls using SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10431: Attachment: SOLR-10431.patch Updated patch, in this patch we will send {{_stateVer_}} for

[jira] [Updated] (SOLR-10431) Make it possible to invoke v2 api calls using SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10431: Attachment: SOLR-10431.patch I think the patch is ready to be committed [~noble.paul] > Make it

[jira] [Updated] (SOLR-10524) Explore in-memory partitioning for processing Overseer queue messages

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10524: Attachment: SOLR-10524.patch Updated patch for this ticket after a discussion with [~noble.paul]

[jira] [Updated] (SOLR-10524) Explore in-memory partitioning for processing Overseer queue messages

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10524: Attachment: SOLR-10524.patch Updated patch for ticket. > Explore in-memory partitioning for

[jira] [Updated] (SOLR-10524) Explore in-memory partitioning for processing Overseer queue messages

[ https://issues.apache.org/jira/browse/SOLR-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10524: Attachment: SOLR-10524.patch Patch for this ticket. Thanks [~noble.paul] for the raw patch. >

[jira] [Assigned] (SOLR-10285) Reduce state messages when there are leader only shards

[ https://issues.apache.org/jira/browse/SOLR-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat reassigned SOLR-10285: --- Assignee: Cao Manh Dat > Reduce state messages when there are leader only shards >

[jira] [Updated] (SOLR-10374) Implement set-policy and remove-policy APIs

[ https://issues.apache.org/jira/browse/SOLR-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10374: Attachment: SOLR-10374.new.patch Updated patch, including {{set-preferences}} api > Implement

[jira] [Comment Edited] (SOLR-10374) Implement set-policy and remove-policy APIs

[ https://issues.apache.org/jira/browse/SOLR-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984571#comment-15984571 ] Cao Manh Dat edited comment on SOLR-10374 at 4/26/17 10:53 AM: ---

[jira] [Commented] (SOLR-10374) Implement set-policy and remove-policy APIs

[ https://issues.apache.org/jira/browse/SOLR-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984571#comment-15984571 ] Cao Manh Dat commented on SOLR-10374: - "set-preferences" api violate the description in

[jira] [Updated] (SOLR-10431) Make it possible to invoke v2 api calls using SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10431: Attachment: SOLR-10431.patch Remove the check

[jira] [Updated] (SOLR-10431) Make it possible to invoke v2 api calls using SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10431: Attachment: SOLR-10431.patch Updated patch for hidding ___v2 path in solrj > Make it possible to

[jira] [Updated] (SOLR-10374) Implement set-policy and remove-policy APIs

[ https://issues.apache.org/jira/browse/SOLR-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10374: Attachment: SOLR-10374.new.patch A new patch reflect the change in design. > Implement set-policy

[jira] [Updated] (SOLR-10374) Implement set-policy and remove-policy APIs

[ https://issues.apache.org/jira/browse/SOLR-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10374: Description: Add {{set-policy}} and {{remove-policy}} APIs for adding, updating and deleting

[jira] [Updated] (SOLR-10433) switch between v2 and v1 endpoints internally in SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10433: Description: There are some bugs in v2 api that I would like to solve in other tickets : - DELETE

[jira] [Commented] (SOLR-10433) switch between v2 and v1 endpoints internally in SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982626#comment-15982626 ] Cao Manh Dat commented on SOLR-10433: - bq. DELETE methods accept async id as a request param Should

[jira] [Commented] (SOLR-10433) switch between v2 and v1 endpoints internally in SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982463#comment-15982463 ] Cao Manh Dat commented on SOLR-10433: - There are some bugs in v2 api that I found when working on this

[jira] [Updated] (SOLR-10431) Make it possible to invoke v2 api calls using SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10431: Attachment: SOLR-10431.patch Updated patch based on [~shalinmangar] review. > Make it possible to

[jira] [Commented] (SOLR-10431) Make it possible to invoke v2 api calls using SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976343#comment-15976343 ] Cao Manh Dat commented on SOLR-10431: - Thanks [~shalinmangar] 1. v2 APIs do use DELETE method. Ex :

[jira] [Updated] (SOLR-10433) switch between v2 and v1 endpoints internally in SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10433: Attachment: SOLR-10433.patch Here are my strategy to accomplish this ticket. It uses code from

[jira] [Resolved] (SOLR-10396) Implement trigger support for nodeLost event type

[ https://issues.apache.org/jira/browse/SOLR-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat resolved SOLR-10396. - Resolution: Fixed > Implement trigger support for nodeLost event type >

[jira] [Commented] (SOLR-10396) Implement trigger support for nodeLost event type

[ https://issues.apache.org/jira/browse/SOLR-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975832#comment-15975832 ] Cao Manh Dat commented on SOLR-10396: - Thanks [~shalinmangar] for review the patch. Committed to

[jira] [Updated] (SOLR-10431) Make it possible to invoke v2 api calls using SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10431: Attachment: SOLR-10431.patch Patch for this ticket. > Make it possible to invoke v2 api calls

[jira] [Assigned] (SOLR-10431) Make it possible to invoke v2 api calls using SolrJ

[ https://issues.apache.org/jira/browse/SOLR-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat reassigned SOLR-10431: --- Assignee: Cao Manh Dat > Make it possible to invoke v2 api calls using SolrJ >

[jira] [Updated] (SOLR-10396) Implement trigger support for nodeLost event type

[ https://issues.apache.org/jira/browse/SOLR-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat updated SOLR-10396: Attachment: SOLR-10396.patch Patch for this ticket. > Implement trigger support for nodeLost event

[jira] [Commented] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second

[ https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973070#comment-15973070 ] Cao Manh Dat commented on SOLR-10420: - [~dragonsinth] This issue is blocker for Solr 6.5.1. So I think

[jira] [Commented] (SOLR-10397) Port 'autoAddReplicas' feature to the policy rules framework and make it work with non-shared filesystems

[ https://issues.apache.org/jira/browse/SOLR-10397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972082#comment-15972082 ] Cao Manh Dat commented on SOLR-10397: - This issue depends on SOLR-10396 > Port 'autoAddReplicas'

[jira] [Assigned] (SOLR-10396) Implement trigger support for nodeLost event type

[ https://issues.apache.org/jira/browse/SOLR-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat reassigned SOLR-10396: --- Assignee: Cao Manh Dat > Implement trigger support for nodeLost event type >

[jira] [Assigned] (SOLR-10397) Port 'autoAddReplicas' feature to the policy rules framework and make it work with non-shared filesystems

[ https://issues.apache.org/jira/browse/SOLR-10397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cao Manh Dat reassigned SOLR-10397: --- Assignee: Cao Manh Dat > Port 'autoAddReplicas' feature to the policy rules framework and

<    5   6   7   8   9   10   11   12   13   14   >