On 10/3/2020 1:42 PM, Ishan Chattopadhyaya wrote:
As you might be aware, the reference_impl branch has a lot of
improvements that we want to see in Solr master. However, it is
currently a large deviation from master and hence the stability and
reliability (though improved in certain aspects)
On 9/1/2020 2:21 PM, Ryan Ernst wrote:
In February a contest was started to design a new logo for Lucene
[jira-issue]. The initial attempt [first-vote] to call a vote resulted
in some confusion on the rules, as well the request for one additional
submission. The second attempt [second-vote]
On 8/6/2020 10:52 AM, Sourav Saha wrote:
However, it is not really removing the duplicates from the results.
Kindly let me know if I am missing something. Any leads would be
appreciated.
Analysis does absolutely nothing to search results. It only affects the
indexed terms, which are not
On 7/9/2020 1:24 AM, Ishan Chattopadhyaya wrote:
I wish to send out something like this to coincide with the release
announcement.
Please review:
https://docs.google.com/document/d/1SdlZVXYgaeZVgL3Xs0ZFHs_RyvdNqNcx3xkEpjdkobU/edit?usp=sharing
Unfortunately, my cwiki/confluence Apache login
On 6/22/2020 1:25 PM, Karthik K G wrote:
It would be helpful if we can get support for the spark-solr connector
to Solr version 8.4.1.
Could you please let us know a tentative date when the latest version
with this support can be released. Many of us will be unblocked with
this release.
I
On 6/18/2020 1:35 AM, Mikhail Khludnev wrote:
I'm challenged with cluster recovery. Think about total failure: ZK
state is lost, however instanceDirs survived since they are mounted via
EBS. Let's say collection is read/only and/or it doesn't have
replicas, just leaders.
Is there a way to
On 6/15/2020 4:08 PM, Ryan Ernst wrote:
Dear Lucene and Solr developers!
In February a contest was started to design a new logo for Lucene [1].
That contest concluded, and I am now (admittedly a little late!) calling
a vote.
The entries are labeled as follows:
A. Submitted by Dustin Haver
On 5/12/2020 1:36 AM, Dawid Weiss wrote:
According to an earlier [DISCUSS] thread on the dev list [2], I am
calling for a vote on the proposal to make Solr a top-level Apache
project (TLP) and separate Lucene and Solr development into two
independent entities.
+1 (pmc)
We should clarify
On 5/10/2020 3:41 PM, Michael McCandless wrote:
I think the costs (I agree: they are high) are a one-time thing, while
the benefits are long term, and accrue/multiply with time. We should
make decisions like this with the long-term benefits in mind.
I expect Lucene and Solr to have long
On 11/30/2019 7:39 AM, Robert Muir wrote:
-1 ... you even went so far as to discourage lucene committers from
attending that meeting, and now its turned around as if its consensus
everywhere and should be applied to lucene too?
I don't think changing things to review-then-commit will help.
On 11/29/2019 11:47 PM, 曾云华 wrote:
I found a lot of 404 bug as below:
FIX THEM:
1 add "index.html" in webapps/solr/js/angular/controllers/cloud.js at
line 961 as below
2 add "index.html" in webapps/solr/partials/cloud.html at line 174 and
220 as below
Usually, you can't change things and
On 11/21/2019 12:12 PM, David Smiley wrote:
*Attended by*: Andrzej Bialecki, Anshum Gupta, Cassandra Targett, Chris
Hostetter, David Smiley, Erick Erickson, Gus Heck, Ishan Chattopadhyaya,
Jan Hoydahl, Jason Gerlowski, Mike D. (Apple), Noble Paul, Shawn Heisey,
Scott Blum, Tomas F. Lobbe
We've had somebody on the Solr mailing list asking questions about our
LTS version.
The thing about this is that we don't really HAVE an LTS version. Our
major version release pace and the way we deal with older branches mean
that a single major version branch is never in a given state for
On 11/7/2019 6:14 PM, Raphael Bircher wrote:
Wich source tree I should build for testing purpose? I heard rumors, that
installing Lucene is a bit rocket science.
I'm here for Solr, and my interest in Lucene is only incidental, because
Solr derives most of its functionality from Lucene.
On 11/7/2019 2:33 AM, Nitin Midas wrote:
We have Apache Solr version 6.2.1 installed on server and we are getting
this warning on Apache Solr log from few days which has affected
performance of solr queries and put latency on our App:
SolrCore [user_details] PERFORMANCE WARNING: Overlapping
A question came across the #solr IRC channel, where the user was seeing
fields in their /admin/luke endpoint about a bunch of fields they used
to use, but are no longer in any current documents. That URL endpoint
provides information about the fields in the index, getting most of that
info
On 10/17/2019 10:58 AM, David Smiley wrote:
Some ideas:
* Add a config file editor to Solr. Not sure if our APIs are sufficient
here; don't want to add another security risk.
It would be VERY useful to have this. It should require explicit admin
action to enable -- not enabled by default,
On 10/6/2019 6:26 PM, Alexandre Rafalovitch wrote:
I am unable to see SOLR-13158 (security issue). I am guessing it was
supposed to be released in 8.1.2 (as per release notes) , which became
8.2 and is now released.
I can't tell if I cannot see it:
1) because its permissions were not fixed due
On 9/30/2019 6:59 AM, Ishan Chattopadhyaya wrote:
I propose that we rename SolrCloud mode to "cluster mode" such that
there shall be "Apache Solr", running in either "standalone mode" or
"cluster mode". We can effect this renaming 9.0 onwards, if we have
consensus.
I am open to any other
On 9/26/2019 11:41 AM, Jyothsna Bavisetti wrote:
I am trying to upgrade Lucene index from 4.6 to 8.0.0. When I'm trying
to upgrade tool using:
java -cp lucene-core.jar:lucene-backward-codecs.jar \
org.apache.lucene.index.IndexUpgrader-delete-prior-commits \
Please let me know any option
On 9/2/2019 9:19 AM, Erick Erickson wrote:
Anyway, it occurred to me that once a max-sized segment is created, _if_ we
write the segments_n file out with the current state of the index, we could
freely delete the segments that were merged into the new one. With 300G indexes
(which I see
On 9/11/2019 4:45 AM, Jan Høydahl wrote:
Upgrading to log4j2 in https://issues.apache.org/jira/browse/SOLR-7887 added
dependency on a bunch of log4j libs to solr-core, e.g. log4j-slf4j-impl which
is a binding for slf4j to log using log4j.
This seems wrong since people who consume solr-core
[
https://issues.apache.org/jira/browse/LUCENE-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917564#comment-16917564
]
Shawn Heisey commented on LUCENE-8951:
--
I didn't see anything come in. Will they sign up my
[
https://issues.apache.org/jira/browse/SOLR-13719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916061#comment-16916061
]
Shawn Heisey commented on SOLR-13719:
-
Looks like we have an oversight in SolrClient and its children
[
https://issues.apache.org/jira/browse/SOLR-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905705#comment-16905705
]
Shawn Heisey commented on SOLR-13464:
-
I'm thinking maybe if the security.json had a place
On 8/6/2019 5:17 PM, Jan Høydahl wrote:
Personally I think the ratio of notifications vs human emails is a bit too
high. I fear external devs who just want to follow the project may get
overwhelmed and unsubscribe.
One suggestion is therefore to add a new list where detailed JIRA comments and
[
https://issues.apache.org/jira/browse/SOLR-13672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898983#comment-16898983
]
Shawn Heisey commented on SOLR-13672:
-
I was just noticing in the screenshot that our error message
[
https://issues.apache.org/jira/browse/SOLR-13672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898980#comment-16898980
]
Shawn Heisey commented on SOLR-13672:
-
I checked the ZK server code for parsing a config file
[
https://issues.apache.org/jira/browse/SOLR-13672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-13672:
Attachment: SOLR-13672.patch
> Admin UI/ZK Status page: Zookeeper 3.5 : 4lw.commands.whitell
[
https://issues.apache.org/jira/browse/SOLR-13672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898853#comment-16898853
]
Shawn Heisey commented on SOLR-13672:
-
I think I would call this a bug in ZK. But since getting
[
https://issues.apache.org/jira/browse/SOLR-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896471#comment-16896471
]
Shawn Heisey commented on SOLR-13665:
-
Yes, the netty jar probably needs to be added to solrj-libs
[
https://issues.apache.org/jira/browse/SOLR-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896411#comment-16896411
]
Shawn Heisey commented on SOLR-13665:
-
The ZK SSL guide says that Netty is required for SSL.
https
[
https://issues.apache.org/jira/browse/SOLR-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey reassigned SOLR-8346:
--
Assignee: Erick Erickson (was: Shawn Heisey)
> Upgrade Zookeeper to version 3.
[
https://issues.apache.org/jira/browse/SOLR-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1677#comment-1677
]
Shawn Heisey commented on SOLR-8346:
[~michelwigbers] This issue is about upgrading the ZK clent code
[
https://issues.apache.org/jira/browse/SOLR-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey reassigned SOLR-8346:
--
Assignee: Shawn Heisey (was: Erick Erickson)
> Upgrade Zookeeper to version 3.
[
https://issues.apache.org/jira/browse/LUCENE-8926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey moved SOLR-13639 to LUCENE-8926:
-
Affects Version/s: (was: 8.1.1)
8.1.1
[
https://issues.apache.org/jira/browse/LUCENE-8925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey moved SOLR-13642 to LUCENE-8925:
-
Affects Version/s: (was: 8.1.1)
8.1.1
[
https://issues.apache.org/jira/browse/SOLR-13642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16887961#comment-16887961
]
Shawn Heisey commented on SOLR-13642:
-
Test2BPostingsBytes is a Lucene test, not a Solr test. Which
[
https://issues.apache.org/jira/browse/SOLR-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey closed SOLR-13620.
---
> Apache Solr warning on 6.2.1
>
>
> Key
[
https://issues.apache.org/jira/browse/SOLR-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey resolved SOLR-13620.
-
Resolution: Invalid
For this project, Jira is not a support portal, it is for bug reports
[
https://issues.apache.org/jira/browse/SOLR-13618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882043#comment-16882043
]
Shawn Heisey commented on SOLR-13618:
-
We need to be careful when deciding just how much rope we
[
https://issues.apache.org/jira/browse/SOLR-13617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882031#comment-16882031
]
Shawn Heisey commented on SOLR-13617:
-
What is the FULL error message? Java exceptions are typically
[
https://issues.apache.org/jira/browse/SOLR-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873561#comment-16873561
]
Shawn Heisey commented on SOLR-5266:
Check to see if there's an actual problem in current
[
https://issues.apache.org/jira/browse/SOLR-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873522#comment-16873522
]
Shawn Heisey commented on SOLR-5266:
HttpSolrServer was renamed to HttpSolrClient in 5.0. In 6.0
[
https://issues.apache.org/jira/browse/SOLR-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870012#comment-16870012
]
Shawn Heisey commented on SOLR-13537:
-
What would be really awesome would be a badge that reflects
[
https://issues.apache.org/jira/browse/SOLR-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864826#comment-16864826
]
Shawn Heisey commented on SOLR-13537:
-
Does the badge reflect the build only or the build+tests?
I
[
https://issues.apache.org/jira/browse/SOLR-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853374#comment-16853374
]
Shawn Heisey commented on SOLR-13452:
-
On the transitive question:
I think that transitive
[
https://issues.apache.org/jira/browse/LUCENE-8807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853203#comment-16853203
]
Shawn Heisey commented on LUCENE-8807:
--
bq, I also checked the new JAR checksums after the change
[
https://issues.apache.org/jira/browse/SOLR-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851956#comment-16851956
]
Shawn Heisey commented on SOLR-8346:
bq. Is there a way to do authenticated/encrypted access to 4lw
[
https://issues.apache.org/jira/browse/SOLR-13492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848491#comment-16848491
]
Shawn Heisey commented on SOLR-13492:
-
This came about while thinking about LUCENE-8814.
> Disal
Shawn Heisey created SOLR-13492:
---
Summary: Disallow explicit GC by default during Solr startup
Key: SOLR-13492
URL: https://issues.apache.org/jira/browse/SOLR-13492
Project: Solr
Issue Type
Shawn Heisey created LUCENE-8814:
Summary: Use forbiddenapis to block explicit GCs
Key: LUCENE-8814
URL: https://issues.apache.org/jira/browse/LUCENE-8814
Project: Lucene - Core
Issue Type
I had a thought I wanted to run by others.
I wondered if maybe we should add -XX:+ExplicitGCInvokesConcurrent or
-XX:+DisableExplicitGC to Solr's default GC tuning.
I checked master with 'git grep System.gc' and the explicit GC calls
only show up in test code and the lucene benchmark,
[
https://issues.apache.org/jira/browse/SOLR-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837559#comment-16837559
]
Shawn Heisey commented on SOLR-13457:
-
I've been putting some thought (but unfortunately not any
[
https://issues.apache.org/jira/browse/SOLR-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16836430#comment-16836430
]
Shawn Heisey commented on SOLR-13394:
-
Regarding the -XX:+PerfDisableSharedMem parameter
[
https://issues.apache.org/jira/browse/SOLR-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835012#comment-16835012
]
Shawn Heisey commented on SOLR-13446:
-
Thanks, for your opinion, [~gerlowskija]!
I'm a little torn
On 5/6/2019 7:37 AM, Erick Erickson wrote:
I want to be clear about my question of whether we’d use Gradle for master and
continue to use Ant for 8x.
It is _totally_ and _completely_ a matter of what would be easiest and up to
the people who are doing the heavy lifting. If moving both to
[
https://issues.apache.org/jira/browse/SOLR-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832929#comment-16832929
]
Shawn Heisey commented on SOLR-13446:
-
{quote}Just let the JVM do it's thing?
{quote}
I'm ambivalent
[
https://issues.apache.org/jira/browse/SOLR-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832786#comment-16832786
]
Shawn Heisey commented on SOLR-13446:
-
For my ideas, I will need somebody to explain how to create
[
https://issues.apache.org/jira/browse/SOLR-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832782#comment-16832782
]
Shawn Heisey commented on SOLR-13446:
-
I'm hoping that I can find some time to work on this issue. I
Shawn Heisey created SOLR-13446:
---
Summary: Improve default heap size and related handling
Key: SOLR-13446
URL: https://issues.apache.org/jira/browse/SOLR-13446
Project: Solr
Issue Type
[
https://issues.apache.org/jira/browse/SOLR-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829606#comment-16829606
]
Shawn Heisey commented on SOLR-13394:
-
bq. The default region size is very large at 16MB. G1GC
[
https://issues.apache.org/jira/browse/SOLR-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825680#comment-16825680
]
Shawn Heisey commented on SOLR-9769:
I see your point, and offer the following:
If Solr is already
[
https://issues.apache.org/jira/browse/SOLR-13414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825580#comment-16825580
]
Shawn Heisey commented on SOLR-13414:
-
bq. and old core was renamed
I don't think you can just
[
https://issues.apache.org/jira/browse/SOLR-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16822748#comment-16822748
]
Shawn Heisey commented on SOLR-13396:
-
bq. Next step: solr starts, and from all the possible
[
https://issues.apache.org/jira/browse/SOLR-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821483#comment-16821483
]
Shawn Heisey commented on SOLR-13394:
-
The reason that I used AggressiveOpts in my GC experiments
[
https://issues.apache.org/jira/browse/SOLR-12461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821378#comment-16821378
]
Shawn Heisey commented on SOLR-12461:
-
I thought LGPL was OK with the Apache License, but I've
[
https://issues.apache.org/jira/browse/SOLR-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16816433#comment-16816433
]
Shawn Heisey commented on SOLR-13396:
-
If I'm not mistaken, I think that delete operations happen
Shawn Heisey created SOLR-13396:
---
Summary: SolrCloud will delete the core data for any core that is
not referenced in the clusterstate
Key: SOLR-13396
URL: https://issues.apache.org/jira/browse/SOLR-13396
Somebody showed up in #solr and asked about configuring multiple CDCR
destinations. They referenced somewhere that somebody had mentioned
setting up multiple handlers, one for each destination.
I have never used CDCR. I checked the documentation, and it looks like
it's configured using a
On 4/5/2019 3:19 AM, Adrien Grand wrote:
Apparently it is possible to ask INFRA to mark branches as
protected[1]. Should we do it for branches that are not expecting new
releases anymore? I think it would make things less trappy. For
instance, backporting to branch_7x is almost for sure a
[
https://issues.apache.org/jira/browse/SOLR-12809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800537#comment-16800537
]
Shawn Heisey commented on SOLR-12809:
-
I was fiddling with my wife's laptop. Noticed that it said
[
https://issues.apache.org/jira/browse/SOLR-12809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797374#comment-16797374
]
Shawn Heisey commented on SOLR-12809:
-
bq. That does seem like a good idea. But I do think it might
[
https://issues.apache.org/jira/browse/SOLR-12809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797345#comment-16797345
]
Shawn Heisey commented on SOLR-12809:
-
bq. I would rather we/Solr not "recommend" any part
On 3/19/2019 12:22 PM, Adrien Grand wrote:
Now that Lucene/Solr 8.0 has shipped I'd like us to consider requiring
Java 11 for 9.0, currently the master branch. We had 18 months between
7.0 and 8.0, so if we assume a similar interval between 8.0 and 9.0
that would mean releasing 9.0 about 2 years
On 3/15/2019 10:52 PM, David Smiley wrote:
In JIRA, should we bother with having "version.x" versions or not, and
only have, say 8.1, 8.2, etc.? I seem to be schizophrenic on this
having thought we did things one way and recently thought the other.
Our release process wiki page[1] makes no
[
https://issues.apache.org/jira/browse/SOLR-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16788202#comment-16788202
]
Shawn Heisey commented on SOLR-9698:
Oh, the patch just submitted has an echo (for debugging
[
https://issues.apache.org/jira/browse/SOLR-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16788174#comment-16788174
]
Shawn Heisey commented on SOLR-9698:
Something that would be immensely useful for testing this sort
On 2/28/2019 6:05 AM, Hemendra Srivastava wrote:
I have done some work on phonetic search, wherein i have modified the
Beider morse filter to work for indian languages (hindi, urdu, bengali,
tamil) as well. I would like to contribute this back to the main solr
codebase. Could someone help me
I'm jumping into this conversation a little bit late. Sorry for any
problems that causes.
On 1/4/2019 9:52 AM, Alexandre Rafalovitch wrote:
What about if a system schema was loaded at a startup implicitly.
Then, if a new schema is loaded and type definition is missing, it is
copied - at that
[
https://issues.apache.org/jira/browse/SOLR-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706480#comment-16706480
]
Shawn Heisey commented on SOLR-13035:
-
My current opinion: The solr.data.home parameter is an expert
[
https://issues.apache.org/jira/browse/SOLR-13026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704801#comment-16704801
]
Shawn Heisey commented on SOLR-13026:
-
Some issues related to problems with computer-based parsing
Shawn Heisey created SOLR-13026:
---
Summary: Admin UI - dataimport status has green bar even when
import fails
Key: SOLR-13026
URL: https://issues.apache.org/jira/browse/SOLR-13026
Project: Solr
On 11/27/2018 7:29 AM, Gus Heck wrote:
Startup logging that happens just on startup should err on the side of
verbosity.
I think this is a good policy.
As I said before, I really do applaud the efforts to shrink the logs and
eliminate cruft. But I don't think that the motivation and goal
On 11/27/2018 3:32 AM, Uwe Schindler wrote:
I'd like to bring one thing into attention: This library conscrypt is
ASF2-licensed, but the JAR files contain binary versions of an OpenSSL fork
named BoringSSL. I'd recommend to check the licensing, because OpenSSL licenses
are a bit strange (some
[
https://issues.apache.org/jira/browse/SOLR-13008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701227#comment-16701227
]
Shawn Heisey commented on SOLR-13008:
-
I had to go look at the docs to figure out what adding
[
https://issues.apache.org/jira/browse/SOLR-13018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey resolved SOLR-13018.
-
Resolution: Invalid
Fix Version/s: (was: 7.3.2)
For this project, Jira
On 11/21/2018 1:40 AM, Jan Høydahl wrote:
It is super easy to change the log level of one particular class or
package
selectively, that's why we have log4j2.xml and also the Admin's
Logging levels menu.
The occational need to see all of the 150 jar files loaded on startup
should not be
solved
On 11/20/2018 9:45 PM, Ian Caldwell wrote:
Yes the bugs were in the std code JIRS created.
https://issues.apache.org/jira/browse/SOLR-13004
https://issues.apache.org/jira/browse/SOLR-13005
Can you attach patches to the issues that fix the problems? We will
need to confirm whether the
[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694230#comment-16694230
]
Shawn Heisey commented on SOLR-13003:
-
Ouch. The jar is five megabytes!
To use it, you'll need
[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694231#comment-16694231
]
Shawn Heisey commented on SOLR-13003:
-
I just realized that I have made a mistake in the patch. I
[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694234#comment-16694234
]
Shawn Heisey commented on SOLR-13003:
-
OK, I was wrong. I thought I had made an error that would
[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-13003:
Attachment: solr-core-7.3.1-SNAPSHOT.jar
> Query Result Cache does not honour maxRamBy
[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-13003:
Attachment: CLRU-logging.patch
> Query Result Cache does not honour maxRamBytes parame
[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694228#comment-16694228
]
Shawn Heisey commented on SOLR-13003:
-
Attached a patch for adding logging. Will attach a custom jar
[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694192#comment-16694192
]
Shawn Heisey commented on SOLR-13003:
-
ConcurrentLRUCache code is identical between 7.3.1 and master
On 11/20/2018 5:34 PM, Alexandre Rafalovitch wrote:
How much of this controlled by log4j property file and we can include
usecases as commented out things to let people choose?
Because we can set the logging very precisely without recompiling.
If we can control it with log4j config, that
[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694114#comment-16694114
]
Shawn Heisey commented on SOLR-13003:
-
ConcurrentLRUCache looks (on first blush) to be coded right
[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694102#comment-16694102
]
Shawn Heisey commented on SOLR-13003:
-
What *EXACTLY* do you have in solrconfig.xml? Can you share
On 11/20/2018 4:09 PM, Jan Høydahl wrote:
In Solr 6.3 (SOLR-6677) we reduced a lot of noisy logging in the default
start/stop scenario. We ended up with a very compact set of log lines. I just
realized that this is getting fatter for every release, and now a solr start -f
looks like this on
1 - 100 of 3810 matches
Mail list logo
