Re: Solr Size Limitation upto 32 kb limitation

Hi Team, Can we have any updates on the below issue? We are awaiting your reply. Thanks, Kranthi kumar.K From: Kranthi Kumar K Sent: Friday, January 4, 2019 5:01:38 PM To: dev@lucene.apache.org Cc: Ananda Babu medida; Srinivasa Reddy Karri Subject: Solr Size

[jira] [Resolved] (SOLR-12806) when strict=false is specified, prioritize node allocation using non strict rules

[ https://issues.apache.org/jira/browse/SOLR-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-12806. --- Resolution: Fixed Fix Version/s: 7.6 > when strict=false is specified, prioritize node

[jira] [Resolved] (SOLR-12023) Autoscaling policy engine shuffles replicas needlessly and can also suggest nonexistent replicas to be moved

[ https://issues.apache.org/jira/browse/SOLR-12023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-12023. --- Resolution: Fixed > Autoscaling policy engine shuffles replicas needlessly and can also suggest >

[jira] [Resolved] (SOLR-12977) Autoscaling policy initialisation tries to fetch metrics from dead nodes

[ https://issues.apache.org/jira/browse/SOLR-12977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-12977. --- Resolution: Fixed > Autoscaling policy initialisation tries to fetch metrics from dead nodes >

[jira] [Commented] (SOLR-5211) updating parent as childless makes old children orphans

[ https://issues.apache.org/jira/browse/SOLR-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744691#comment-16744691 ] mosh commented on SOLR-5211: {quote}What if we delete the complete block and create the block again and add

[JENKINS] Lucene-Solr-repro - Build # 2687 - Unstable

Build: https://builds.apache.org/job/Lucene-Solr-repro/2687/ [...truncated 28 lines...] [repro] Jenkins log URL: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-master/1235/consoleText [repro] Revision: d970375cd2f2357b6a8da5ac67ef994f8d43 [repro] Ant options:

[JENKINS] Lucene-Solr-BadApples-NightlyTests-7.x - Build # 44 - Still Unstable

Build: https://builds.apache.org/job/Lucene-Solr-BadApples-NightlyTests-7.x/44/ 3 tests failed. FAILED: org.apache.solr.cloud.ChaosMonkeyNothingIsSafeTest.test Error Message: The Monkey ran for over 60 seconds and no jetties were stopped - this is worth investigating! Stack Trace:

[jira] [Issue Comment Deleted] (SOLR-5211) updating parent as childless makes old children orphans

[ https://issues.apache.org/jira/browse/SOLR-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucky Sharma updated SOLR-5211: --- Comment: was deleted (was: Yes, that will take 2 calls, I have implemented this with 7.2.1 and 6.6,

[jira] [Resolved] (SOLR-12424) Search trigger does not accept handler

[ https://issues.apache.org/jira/browse/SOLR-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cassandra Targett resolved SOLR-12424. -- Resolution: Fixed Fix Version/s: 7.4 The documentation was updated for 7.4, so

[jira] [Commented] (SOLR-12815) Implement maxOps limit for IndexSizeTrigger

[ https://issues.apache.org/jira/browse/SOLR-12815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744644#comment-16744644 ] Cassandra Targett commented on SOLR-12815: -- [~ab], this appears in CHANGES.txt for 7.6, can it

[jira] [Commented] (LUCENE-8642) RamUsageTester.sizeOf ignores arrays and collections if --illegal-access=deny

[ https://issues.apache.org/jira/browse/LUCENE-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744639#comment-16744639 ] Mike Sokolov commented on LUCENE-8642: -- I feel like there is a value to a partial solution here,

[jira] [Commented] (LUCENE-8635) Lazy loading Lucene FST offheap using mmap

[ https://issues.apache.org/jira/browse/LUCENE-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744621#comment-16744621 ] Mike Sokolov commented on LUCENE-8635: -- I used the wikimedia2m data set for the second set of tests

Re: [jira] [Commented] (LUCENE-8635) Lazy loading Lucene FST offheap using mmap

I used the wikimedia2m data set for the second set of tests (the first test was on a tiny index - 10k docs) -- at least I think I did! I am kind of new to the benchmarking game. I ran the becnhmarks with python src/python/localrun.py -source wikimedium2m, and I can see that the index dir is 861M.

[GitHub] MighTguY commented on issue #537: LUCENE-8640: added changes for the validation of valid dateString

MighTguY commented on issue #537: LUCENE-8640: added changes for the validation of valid dateString URL: https://github.com/apache/lucene-solr/pull/537#issuecomment-455009248 Raised another PR https://github.com/apache/lucene-solr/pull/538

[GitHub] MighTguY commented on issue #537: LUCENE-8640: added changes for the validation of valid dateString

MighTguY commented on issue #537: LUCENE-8640: added changes for the validation of valid dateString URL: https://github.com/apache/lucene-solr/pull/537#issuecomment-455009176 Closing this request, Due to my forked repo issues.

[GitHub] MighTguY closed pull request #537: LUCENE-8640: added changes for the validation of valid dateString

MighTguY closed pull request #537: LUCENE-8640: added changes for the validation of valid dateString URL: https://github.com/apache/lucene-solr/pull/537 This is an automated message from the Apache Git Service. To respond

[GitHub] MighTguY opened a new pull request #538: LUCENE-8640: added changes for the validation of valid dateString

MighTguY opened a new pull request #538: LUCENE-8640: added changes for the validation of valid dateString URL: https://github.com/apache/lucene-solr/pull/538 This is an automated message from the Apache Git Service. To

[GitHub] MighTguY closed pull request #538: LUCENE-8640: added changes for the validation of valid dateString

MighTguY closed pull request #538: LUCENE-8640: added changes for the validation of valid dateString URL: https://github.com/apache/lucene-solr/pull/538 This is an automated message from the Apache Git Service. To respond

[GitHub] MighTguY opened a new pull request #538: LUCENE-8640: added changes for the validation of valid dateString

MighTguY opened a new pull request #538: LUCENE-8640: added changes for the validation of valid dateString URL: https://github.com/apache/lucene-solr/pull/538 This is an automated message from the Apache Git Service. To

[jira] [Commented] (SOLR-13007) Use javabin instead of JSON to send messages to overseer

[ https://issues.apache.org/jira/browse/SOLR-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744575#comment-16744575 ] Noble Paul commented on SOLR-13007: --- The fix itself is pretty easy. I didn't do it because it can cause

[jira] [Updated] (SOLR-12467) allow to change the autoscaling configuration via SolrJ

[ https://issues.apache.org/jira/browse/SOLR-12467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cassandra Targett updated SOLR-12467: - Component/s: AutoScaling > allow to change the autoscaling configuration via SolrJ >

[jira] [Commented] (SOLR-12868) Request forwarding for v2 API is broken

[ https://issues.apache.org/jira/browse/SOLR-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744568#comment-16744568 ] Cassandra Targett commented on SOLR-12868: -- [~noble.paul], here's *another* issue that appears

[JENKINS] Lucene-Solr-Tests-8.x - Build # 7 - Unstable

Build: https://builds.apache.org/job/Lucene-Solr-Tests-8.x/7/ 2 tests failed. FAILED: org.apache.solr.cloud.DeleteReplicaTest.deleteReplicaFromClusterStateLegacy Error Message: Timeout waiting for replica get deleted Timeout waiting to see state for collection=deleteFromClusterState_true

[jira] [Commented] (LUCENE-8635) Lazy loading Lucene FST offheap using mmap

[ https://issues.apache.org/jira/browse/LUCENE-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744538#comment-16744538 ] Michael McCandless commented on LUCENE-8635: Thanks [~sokolov] – those numbers look quite a

[jira] [Issue Comment Deleted] (LUCENE-5755) Explore alternative build systems

[ https://issues.apache.org/jira/browse/LUCENE-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kroz updated LUCENE-5755: -- Comment: was deleted (was: +1) > Explore alternative build systems >

[jira] [Commented] (LUCENE-5755) Explore alternative build systems

[ https://issues.apache.org/jira/browse/LUCENE-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744532#comment-16744532 ] Vladimir Kroz commented on LUCENE-5755: --- +1 > Explore alternative build systems >

[jira] [Commented] (LUCENE-8635) Lazy loading Lucene FST offheap using mmap

[ https://issues.apache.org/jira/browse/LUCENE-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744519#comment-16744519 ] Mike Sokolov commented on LUCENE-8635: -- Right, it seems crazy that makes a difference. I guess

[JENKINS] Lucene-Solr-8.x-MacOSX (64bit/jdk1.8.0) - Build # 11 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-MacOSX/11/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.client.solrj.impl.CloudSolrClientTest Error Message: ObjectTracker found 5 object(s) that were not

[jira] [Commented] (SOLR-12373) DocBasedVersionConstraintsProcessor doesn't work when schema has required fields

[ https://issues.apache.org/jira/browse/SOLR-12373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744492#comment-16744492 ] Hoss Man commented on SOLR-12373: - Tomas: LGTM ... although I would suggest pruning your

[JENKINS] Lucene-Solr-NightlyTests-master - Build # 1752 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-master/1752/ 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.LeaderTragicEventTest Error Message: ObjectTracker found 1 object(s) that were not released!!! [MockDirectoryWrapper]

[jira] [Commented] (SOLR-8291) NPE calling export handler when useFilterForSortedQuery=true

[ https://issues.apache.org/jira/browse/SOLR-8291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744483#comment-16744483 ] Rahul Goswami commented on SOLR-8291: - Facing the same issue on 7.2.1 while using /export handler...

[jira] [Commented] (SOLR-13140) Harden SearchRateTriggerIntegrationTest

[ https://issues.apache.org/jira/browse/SOLR-13140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744468#comment-16744468 ] Andrzej Bialecki commented on SOLR-13140: -- The internal traffic is between replicas and shard

[jira] [Commented] (SOLR-12977) Autoscaling policy initialisation tries to fetch metrics from dead nodes

[ https://issues.apache.org/jira/browse/SOLR-12977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744451#comment-16744451 ] Cassandra Targett commented on SOLR-12977: -- [~noble.paul], This appears in CHANGES.txt for 7.6,

[jira] [Commented] (SOLR-5211) updating parent as childless makes old children orphans

[ https://issues.apache.org/jira/browse/SOLR-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1675#comment-1675 ] David Smiley commented on SOLR-5211: {quote}I'm unclear on your meaning. I would think the default

[jira] [Resolved] (SOLR-12908) Add a default set of cluster preferences

[ https://issues.apache.org/jira/browse/SOLR-12908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cassandra Targett resolved SOLR-12908. -- Resolution: Not A Problem Marking as Not a Problem. I have some doc changes I will

[jira] [Commented] (SOLR-12023) Autoscaling policy engine shuffles replicas needlessly and can also suggest nonexistent replicas to be moved

[ https://issues.apache.org/jira/browse/SOLR-12023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744433#comment-16744433 ] Cassandra Targett commented on SOLR-12023: -- Did the commits here get straightened out? Is this

[jira] [Commented] (SOLR-12806) when strict=false is specified, prioritize node allocation using non strict rules

[ https://issues.apache.org/jira/browse/SOLR-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744426#comment-16744426 ] Cassandra Targett commented on SOLR-12806: -- [~noble.paul], so is this fixed? It's in 7.6

[JENKINS] Lucene-Solr-repro - Build # 2685 - Still Unstable

Build: https://builds.apache.org/job/Lucene-Solr-repro/2685/ [...truncated 28 lines...] [repro] Jenkins log URL: https://builds.apache.org/job/Lucene-Solr-NightlyTests-master/1751/consoleText [repro] Revision: d965b3547e2fb87cb7551687bae312a0ff62e526 [repro] Ant options: -Dtests.multiplier=2

[jira] [Commented] (LUCENE-8635) Lazy loading Lucene FST offheap using mmap

[ https://issues.apache.org/jira/browse/LUCENE-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744419#comment-16744419 ] Ankit Jain commented on LUCENE-8635: Thanks [~sokolov] for updating patch and doing another run. As

[jira] [Commented] (SOLR-12903) Query Source Tracker custom Solr component

[ https://issues.apache.org/jira/browse/SOLR-12903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744353#comment-16744353 ] Hoss Man commented on SOLR-12903: - So, my first tought when reviewing this patch is that the entire "qi"

[jira] [Commented] (LUCENE-8635) Lazy loading Lucene FST offheap using mmap

[ https://issues.apache.org/jira/browse/LUCENE-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744344#comment-16744344 ] Mike Sokolov commented on LUCENE-8635: -- Following a suggestion from ~mikemccand I tried a slightly

[JENKINS] Lucene-Solr-SmokeRelease-8.x - Build # 4 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-8.x/4/ No tests ran. Build Log: [...truncated 23487 lines...] [asciidoctor:convert] asciidoctor: ERROR: about-this-guide.adoc: line 1: invalid part, must have at least one section (e.g., chapter, appendix, etc.) [asciidoctor:convert]

[jira] [Comment Edited] (LUCENE-8635) Lazy loading Lucene FST offheap using mmap

[ https://issues.apache.org/jira/browse/LUCENE-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744344#comment-16744344 ] Mike Sokolov edited comment on LUCENE-8635 at 1/16/19 6:54 PM: --- Following

[jira] [Updated] (LUCENE-8635) Lazy loading Lucene FST offheap using mmap

[ https://issues.apache.org/jira/browse/LUCENE-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Sokolov updated LUCENE-8635: - Attachment: ra.patch > Lazy loading Lucene FST offheap using mmap >

[JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk-9) - Build # 5022 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/5022/ Java: 64bit/jdk-9 -XX:+UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.ChaosMonkeyNothingIsSafeWithPullReplicasTest Error Message: ObjectTracker found 5 object(s)

[jira] [Comment Edited] (SOLR-13126) Inconsistent score in debug and result with multiple multiplicative boosts

[ https://issues.apache.org/jira/browse/SOLR-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744256#comment-16744256 ] Thomas Aglassinger edited comment on SOLR-13126 at 1/16/19 5:24 PM:

[jira] [Comment Edited] (SOLR-13126) Inconsistent score in debug and result with multiple multiplicative boosts

[ https://issues.apache.org/jira/browse/SOLR-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744256#comment-16744256 ] Thomas Aglassinger edited comment on SOLR-13126 at 1/16/19 5:23 PM:

[jira] [Commented] (SOLR-5211) updating parent as childless makes old children orphans

[ https://issues.apache.org/jira/browse/SOLR-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744268#comment-16744268 ] Lucky Sharma commented on SOLR-5211: Yes, that will take 2 calls, I have implemented this with 7.2.1

[jira] [Comment Edited] (LUCENE-8634) LatLonShape: Query with the same polygon that is indexed might not match

[ https://issues.apache.org/jira/browse/LUCENE-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744267#comment-16744267 ] Ignacio Vera edited comment on LUCENE-8634 at 1/16/19 5:19 PM: --- Actually,

[jira] [Commented] (LUCENE-8634) LatLonShape: Query with the same polygon that is indexed might not match

[ https://issues.apache.org/jira/browse/LUCENE-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744267#comment-16744267 ] Ignacio Vera commented on LUCENE-8634: -- Actually, in the example of the patch, the resulting

[jira] [Commented] (LUCENE-8634) LatLonShape: Query with the same polygon that is indexed might not match

[ https://issues.apache.org/jira/browse/LUCENE-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744266#comment-16744266 ] Ignacio Vera commented on LUCENE-8634: -- It won't fail as there are no checks for intersection

[jira] [Comment Edited] (SOLR-13126) Inconsistent score in debug and result with multiple multiplicative boosts

[ https://issues.apache.org/jira/browse/SOLR-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744256#comment-16744256 ] Thomas Aglassinger edited comment on SOLR-13126 at 1/16/19 5:16 PM:

[jira] [Comment Edited] (SOLR-13126) Inconsistent score in debug and result with multiple multiplicative boosts

[ https://issues.apache.org/jira/browse/SOLR-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744256#comment-16744256 ] Thomas Aglassinger edited comment on SOLR-13126 at 1/16/19 5:15 PM:

[jira] [Commented] (SOLR-5211) updating parent as childless makes old children orphans

[ https://issues.apache.org/jira/browse/SOLR-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744264#comment-16744264 ] Yosef Brown commented on SOLR-5211: --- That's one workaround I am planning to try (on 7.5) -- delete the

[jira] [Updated] (SOLR-13126) Inconsistent score in debug and result with multiple multiplicative boosts

[ https://issues.apache.org/jira/browse/SOLR-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Aglassinger updated SOLR-13126: -- Attachment: 0002-SOLR-13126-Added-test-case.patch

[jira] [Commented] (SOLR-13126) Inconsistent score in debug and result with multiple multiplicative boosts

[ https://issues.apache.org/jira/browse/SOLR-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744256#comment-16744256 ] Thomas Aglassinger commented on SOLR-13126: --- We digged in further and seem to have found the

[jira] [Commented] (LUCENE-8634) LatLonShape: Query with the same polygon that is indexed might not match

[ https://issues.apache.org/jira/browse/LUCENE-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744233#comment-16744233 ] Adrien Grand commented on LUCENE-8634: -- I think it depends what happens in such a case: would we

[jira] [Updated] (SOLR-12955) Refactor DistributedUpdateProcessor

[ https://issues.apache.org/jira/browse/SOLR-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bar Rotstein updated SOLR-12955: Attachment: SOLR-12955.patch > Refactor DistributedUpdateProcessor >

[jira] [Commented] (SOLR-12955) Refactor DistributedUpdateProcessor

[ https://issues.apache.org/jira/browse/SOLR-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744229#comment-16744229 ] Bar Rotstein commented on SOLR-12955: - Uploaded a new patch file, based on the changes made in PR

[jira] [Commented] (SOLR-13007) Use javabin instead of JSON to send messages to overseer

[ https://issues.apache.org/jira/browse/SOLR-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744225#comment-16744225 ] Bar Rotstein commented on SOLR-13007: - {quote}This is a micro optimization. Not very essential and it

Re: Re: Admin UI - Collections Management

Thanks Jan – I agree it makes sense to have the operation in the collection -> … -> replica area, since it’s a related function. On the other hand, when I’m looking to move replicas around, I’m interested in seeing the replicas grouped by server rather than shard. Seems like the overlap may be

[jira] [Commented] (LUCENE-8634) LatLonShape: Query with the same polygon that is indexed might not match

[ https://issues.apache.org/jira/browse/LUCENE-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744211#comment-16744211 ] Ignacio Vera commented on LUCENE-8634: -- Mostly, the Morton optimisation order the points on the

[jira] [Commented] (SOLR-5211) updating parent as childless makes old children orphans

[ https://issues.apache.org/jira/browse/SOLR-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744208#comment-16744208 ] Lucky Sharma commented on SOLR-5211: What if we delete the complete block and create the block again

[jira] [Commented] (LUCENE-8634) LatLonShape: Query with the same polygon that is indexed might not match

[ https://issues.apache.org/jira/browse/LUCENE-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744180#comment-16744180 ] Adrien Grand commented on LUCENE-8634: -- bq. This is the same case as in the tessellator The

[jira] [Resolved] (LUCENE-8639) SeqNo accounting in IW is broken if many threads start indexing while we flush.

[ https://issues.apache.org/jira/browse/LUCENE-8639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Willnauer resolved LUCENE-8639. - Resolution: Fixed Fix Version/s: master (9.0) 7.7

[jira] [Commented] (LUCENE-8639) SeqNo accounting in IW is broken if many threads start indexing while we flush.

[ https://issues.apache.org/jira/browse/LUCENE-8639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744168#comment-16744168 ] ASF subversion and git services commented on LUCENE-8639: - Commit

[jira] [Commented] (LUCENE-8639) SeqNo accounting in IW is broken if many threads start indexing while we flush.

[ https://issues.apache.org/jira/browse/LUCENE-8639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744165#comment-16744165 ] ASF subversion and git services commented on LUCENE-8639: - Commit

[jira] [Commented] (LUCENE-8634) LatLonShape: Query with the same polygon that is indexed might not match

[ https://issues.apache.org/jira/browse/LUCENE-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744162#comment-16744162 ] Ignacio Vera commented on LUCENE-8634: -- {quote}Are there concerns regarding the fact that a polygon

[jira] [Commented] (LUCENE-8639) SeqNo accounting in IW is broken if many threads start indexing while we flush.

[ https://issues.apache.org/jira/browse/LUCENE-8639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744159#comment-16744159 ] ASF subversion and git services commented on LUCENE-8639: - Commit

[GitHub] s1monw merged pull request #535: LUCENE-8639: Prevent new threadstates from being created while we cut over to a new delete queue

s1monw merged pull request #535: LUCENE-8639: Prevent new threadstates from being created while we cut over to a new delete queue URL: https://github.com/apache/lucene-solr/pull/535 This is an automated message from the

[jira] [Commented] (SOLR-5211) updating parent as childless makes old children orphans

[ https://issues.apache.org/jira/browse/SOLR-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744145#comment-16744145 ] Yosef Brown commented on SOLR-5211: --- [~dsmiley] bq. a delete-by-id would also only delete a root

[jira] [Commented] (LUCENE-8644) Pass token types to QueryBuilder.newSynonymQuery()

[ https://issues.apache.org/jira/browse/LUCENE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744132#comment-16744132 ] Alan Woodward commented on LUCENE-8644: --- Multi-term synonyms go through analyzeGraphPhrase and so

[GitHub] mikemccand commented on issue #535: LUCENE-8639: Prevent new threadstates from being created while we cut over to a new delete queue

mikemccand commented on issue #535: LUCENE-8639: Prevent new threadstates from being created while we cut over to a new delete queue URL: https://github.com/apache/lucene-solr/pull/535#issuecomment-454811616 I like the test case!!

[JENKINS] Lucene-Solr-7.x-Linux (64bit/jdk1.8.0_172) - Build # 3409 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-7.x-Linux/3409/ Java: 64bit/jdk1.8.0_172 -XX:+UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.cloud.TestCloudSearcherWarming.testRepFactor1LeaderStartup Error Message: No live SolrServers available to handle this

[jira] [Commented] (LUCENE-8633) Remove term weighting from interval scoring

[ https://issues.apache.org/jira/browse/LUCENE-8633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744076#comment-16744076 ] ASF subversion and git services commented on LUCENE-8633: - Commit

[jira] [Resolved] (LUCENE-8633) Remove term weighting from interval scoring

[ https://issues.apache.org/jira/browse/LUCENE-8633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Woodward resolved LUCENE-8633. --- Resolution: Fixed Fix Version/s: master (9.0) 8.0 > Remove term

[jira] [Commented] (LUCENE-8633) Remove term weighting from interval scoring

[ https://issues.apache.org/jira/browse/LUCENE-8633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744077#comment-16744077 ] ASF subversion and git services commented on LUCENE-8633: - Commit

[jira] [Comment Edited] (SOLR-13141) replicationFactor param cause problems with CDCR

[ https://issues.apache.org/jira/browse/SOLR-13141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743816#comment-16743816 ] Krzysztof Watral edited comment on SOLR-13141 at 1/16/19 2:10 PM: --

[GitHub] mikemccand commented on issue #535: LUCENE-8639: Prevent new threadstates from being created while we cut over to a new delete queue

mikemccand commented on issue #535: LUCENE-8639: Prevent new threadstates from being created while we cut over to a new delete queue URL: https://github.com/apache/lucene-solr/pull/535#issuecomment-454787650 LGTM -- sneaky.

[jira] [Comment Edited] (LUCENE-8640) validate delimiters when parsing date ranges

[ https://issues.apache.org/jira/browse/LUCENE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744039#comment-16744039 ] Lucky Sharma edited comment on LUCENE-8640 at 1/16/19 1:30 PM: --- yes It

[jira] [Commented] (LUCENE-8640) validate delimiters when parsing date ranges

[ https://issues.apache.org/jira/browse/LUCENE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744039#comment-16744039 ] Lucky Sharma commented on LUCENE-8640: -- yes > validate delimiters when parsing date ranges >

[jira] [Updated] (LUCENE-8640) validate delimiters when parsing date ranges

[ https://issues.apache.org/jira/browse/LUCENE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucky Sharma updated LUCENE-8640: - Attachment: mypatch.patch > validate delimiters when parsing date ranges >

[jira] [Updated] (LUCENE-8640) validate delimiters when parsing date ranges

[ https://issues.apache.org/jira/browse/LUCENE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucky Sharma updated LUCENE-8640: - Attachment: (was: mypatch.patch) > validate delimiters when parsing date ranges >

Re: Admin UI - Collections Management

I think perhaps this belongs in the Collections -> coll_name -> Shards -> Replicas screen, where you can already delete and add a replica to a shard. That screen has a dropdown to select what node the new replica should be created on. So if you add a MOVE button next to the DELETE button, and

[jira] [Commented] (LUCENE-8634) LatLonShape: Query with the same polygon that is indexed might not match

[ https://issues.apache.org/jira/browse/LUCENE-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743997#comment-16743997 ] Adrien Grand commented on LUCENE-8634: -- Thanks Ignacio. I understand how it makes things better but

[jira] [Commented] (LUCENE-8640) validate delimiters when parsing date ranges

[ https://issues.apache.org/jira/browse/LUCENE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743949#comment-16743949 ] Mikhail Khludnev commented on LUCENE-8640: -- does it pass Solr's DateRangeFieldTest ? >

[jira] [Updated] (LUCENE-8640) validate delimiters when parsing date ranges

[ https://issues.apache.org/jira/browse/LUCENE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucky Sharma updated LUCENE-8640: - Attachment: (was: mypatch.patch) > validate delimiters when parsing date ranges >

[jira] [Updated] (LUCENE-8640) validate delimiters when parsing date ranges

[ https://issues.apache.org/jira/browse/LUCENE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucky Sharma updated LUCENE-8640: - Attachment: mypatch.patch > validate delimiters when parsing date ranges >

[JENKINS] Lucene-Solr-master-Linux (64bit/jdk-9.0.4) - Build # 23529 - Still unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/23529/ Java: 64bit/jdk-9.0.4 -XX:-UseCompressedOops -XX:+UseSerialGC 4 tests failed. FAILED: org.apache.lucene.search.TermInSetQueryTest.testRamBytesUsed Error Message: expected:<237624.0> but was:<3456.0> Stack Trace:

[GitHub] MighTguY opened a new pull request #537: LUCENE-8640: added changes for the validation of valid dateString

MighTguY opened a new pull request #537: LUCENE-8640: added changes for the validation of valid dateString URL: https://github.com/apache/lucene-solr/pull/537 This is an automated message from the Apache Git Service. To

[jira] [Commented] (LUCENE-8640) validate delimiters when parsing date ranges

[ https://issues.apache.org/jira/browse/LUCENE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743898#comment-16743898 ] Lucky Sharma commented on LUCENE-8640: -- Please review the patch for the same > validate delimiters

[jira] [Updated] (LUCENE-8640) validate delimiters when parsing date ranges

[ https://issues.apache.org/jira/browse/LUCENE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucky Sharma updated LUCENE-8640: - Attachment: mypatch.patch > validate delimiters when parsing date ranges >

[jira] [Commented] (LUCENE-8633) Remove term weighting from interval scoring

[ https://issues.apache.org/jira/browse/LUCENE-8633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743886#comment-16743886 ] Jim Ferenczi commented on LUCENE-8633: -- Thanks Alan, +1 the patch looks good. > Remove term

[jira] [Commented] (LUCENE-8644) Pass token types to QueryBuilder.newSynonymQuery()

[ https://issues.apache.org/jira/browse/LUCENE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743890#comment-16743890 ] Jim Ferenczi commented on LUCENE-8644: -- I like the idea but I wonder how it would work for

[jira] [Commented] (LUCENE-8644) Pass token types to QueryBuilder.newSynonymQuery()

[ https://issues.apache.org/jira/browse/LUCENE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743871#comment-16743871 ] Alan Woodward commented on LUCENE-8644: --- This patch changes the signature of newSynonymQuery from

[jira] [Commented] (LUCENE-8643) TestLatLonLineShapeQueries.testRandomBig fails with suite timeout (simple text codec used)

[ https://issues.apache.org/jira/browse/LUCENE-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743869#comment-16743869 ] Ignacio Vera commented on LUCENE-8643: -- I agree it is over-iterating and that's the job of CI. And

[jira] [Commented] (LUCENE-8640) validate delimiters when parsing date ranges

[ https://issues.apache.org/jira/browse/LUCENE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743867#comment-16743867 ] Lucky Sharma commented on LUCENE-8640: -- [~mkhludnev] will this be count as a valid date

[jira] [Created] (LUCENE-8644) Pass token types to QueryBuilder.newSynonymQuery()

Alan Woodward created LUCENE-8644: - Summary: Pass token types to QueryBuilder.newSynonymQuery() Key: LUCENE-8644 URL: https://issues.apache.org/jira/browse/LUCENE-8644 Project: Lucene - Core

[jira] [Updated] (LUCENE-8644) Pass token types to QueryBuilder.newSynonymQuery()

[ https://issues.apache.org/jira/browse/LUCENE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Woodward updated LUCENE-8644: -- Attachment: LUCENE-8644.patch > Pass token types to QueryBuilder.newSynonymQuery() >

[jira] [Commented] (LUCENE-8643) TestLatLonLineShapeQueries.testRandomBig fails with suite timeout (simple text codec used)

[ https://issues.apache.org/jira/browse/LUCENE-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743857#comment-16743857 ] Dawid Weiss commented on LUCENE-8643: - I think it's just terribly slow if it hits a high number of

  1   2   >