ndle the
> buffer when it reaches a certain size.
>
> -Yonik
>
>
>> On Thu, Sep 17, 2020 at 11:48 AM Christopher Schultz <
>> ch...@christopherschultz.net> wrote:
>>
>> All,
>>
>> Is this an appropriate forum for asking questions about how t
All,
Is this an appropriate forum for asking questions about how to use
Noggit? The Github doesn't have any discussions available and filing an
"issue" to ask a question is kinda silly. I'm happy to be redirected to
the right place if this isn't appropriate.
I've been able to figure out most
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
Ping. Any options for no-downtime TLS reconfiguration?
- -chris
On 4/23/20 11:35, Christopher Schultz wrote:
> All,
>
> Does anyone know if it is possible to reconfigure Solr's TLS
> configuration (specifically, th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rahul,
On 4/23/20 21:49, dhurandar S wrote:
> Thank you for your reply. The reason we are looking for S3 is since
> the volume is close to 10 Petabytes. We are okay to have higher
> latency of say twice or thrice that of placing data on the local
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
Does anyone know if it is possible to reconfigure Solr's TLS
configuration (specifically, the server key and certificate) without a
restart?
I'm looking for a zero-downtime situation with a single-server and an
updated TLS certificate.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kushal,
On 8/26/19 07:52, Khare, Kushal (MIND) wrote:
> This is Kushal Khare, a new addition to the user-list. I started
> working with Solr few days ago for implementing it in my project.
>
> Now, I have the basics done, and reached the query
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I'm getting a failure to start my Solr instance. Here's the error from
the console log:
Error: Exception thrown by the agent : java.net.MalformedURLException:
Local host name unknown: java.net.UnknownHostException: [hostname]:
[hostname]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Paul,
On 6/7/19 11:02, Paul wrote:
> Can someone please outline how to use mutual TLS 1.2 with SOLR. Or,
> point me at docs/tutorials/other where I can read up further on
> this (version currently onsite is SOLR 7.6).
Here's a copy/paste from our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel,
On 6/3/19 16:26, Davis, Daniel (NIH/NLM) [C] wrote:
> I think the sweet spot of Cassandra and Solr should be mentioned
> in this discussion. Cassandra is more scalable/clusterable than
> an RDBMS, without losing all of the structure that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ralph,
On 6/2/19 16:32, Ralph Soika wrote:
> The whole system is highly transactional as it runs on Java EE with
> JPA and Session EJBs.
And you write-through from your application -> RDBMS -> Lucene/Solr?
How are you handling commits (both soft
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dimitris,
On 6/1/18 02:46, Dimitris Kardarakos wrote:
> Thanks a lot Shawn. I had tried with the documented approach, but
> since I use SolrClient.add to add documents to the index, I could
> not "port" the documented approach to my case (probably
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn and Paul,
On 5/23/19 08:57, Shawn Heisey wrote:
> On 5/23/2019 5:45 AM, Paul wrote:
>> unable to find valid certification path to requested target
>
> This seems to be the root of your problem with the connection to
> SQL server.
>
> If I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 3/14/19 10:46, Shawn Heisey wrote:
> On 3/14/2019 8:23 AM, Christopher Schultz wrote:
>> I believe that the only thing I want to do is to set the
>> autoSoftCommit value to something "reasonable". I'll probably
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I recently had a situation where a document wasn't findable in a
fairly small Solr core/collection and I didn't see any errors in
either the application using Solr or within Solr itself. A Solr
service restart caused the document to become
> there if you think that'd be an improvement.
I've added some comments and a proposed fix that meets *my* needs, but
I want to make sure that it will be useful for others (and not just my
specific use-case).
Thanks,
- -chris
> On Tue, Feb 12, 2019 at 5:09 PM Christopher Schultz
> wro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello, everyone.
I'm trying to get some information about a (fairly) simple case when a
user is searching using a wide-open query where they can type in
anything they want, including field-names. Of course, it's possible
that they will try to enter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Erick,
On 1/7/19 11:52, Erick Erickson wrote:
> Images do not come through, so we don't see what you're seeing.
>
> That said, I'd expect page faults to happen:
>
> 1> when indexing. Besides what you'd expect (new segments written
> to disk),
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 11/29/18 18:53, Shawn Heisey wrote:
> On 11/29/2018 4:41 PM, Christopher Schultz wrote:
>> When mine returned (with wait=true as a request parameter), I got
>> a JSON response telling me how long it took.
>
> That'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 11/29/18 17:56, Shawn Heisey wrote:
> On 11/28/2018 6:22 PM, Wei wrote:
>> I use the following http request to start solr index
>> optimization:
>>
>> http://localhost:8983/solr//update?skipError=true -F
>> stream.body=' '
>>
>> The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Wei,
On 11/28/18 20:22, Wei wrote:
> Hi,
>
> I use the following http request to start solr index optimization:
>
> http://localhost:8983/solr//update?skipError=true -F
> stream.body=' '
>
>
> The request returns status code 200 shortly, but
ally a untar/stop/ln/start operation as long as testing goes
well.
- -chris
> On Tue, Nov 27, 2018 at 2:11 PM Shawn Heisey
> wrote:
>>
>> On 11/27/2018 10:04 AM, Christopher Schultz wrote:
>>> So, it's pretty much like GC promotion: the number of live
>>> objects is r
lly "optimizing" (or merging) the index?
Thanks,
- -chris
>> On Nov 27, 2018, at 9:04 AM, Christopher Schultz
>> wrote:
>>
> Shawn,
>
> On 11/27/18 11:01, Shawn Heisey wrote:
>>>> On 11/27/2018 7:47 AM, Christopher Schultz wrote:
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 11/27/18 11:01, Shawn Heisey wrote:
> On 11/27/2018 7:47 AM, Christopher Schultz wrote:
>> I've got a single-core Solr instance with something like 1M small
>> documents in it. It contains user information for fast-lookups,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I've got a single-core Solr instance with something like 1M small
documents in it. It contains user information for fast-lookups, and it
gets updated any time relevant user-info changes.
Here's the basic info from the Core Dashboard:
Last
mit the native memory using OS limits (or, using Docker,
simply make it look like there is less system memory) then you haven't
actually achieved anything. You could have done that simply by
lowering heap values and avoided the complexity of Docker, etc.
- -chris
> On 11.10.2018 16:45, Christopher
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 10/11/18 12:54 AM, Shawn Heisey wrote:
> On 10/10/2018 10:08 PM, Sourav Moitra wrote:
>> We have a Solr server with 8gb of memory. We are using solr in
>> cloud mode, solr version is 7.5, Java version is Oracle Java 9
>> and settings for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 9/27/18 10:00, Shawn Heisey wrote:
> On 9/27/2018 7:24 AM, Kimber, Mike wrote:
>> I'm trying to determine if there is any health check available
>> to determine the above and then if the issue happens then an
>> automated mechanism in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jeff,
On 9/26/18 11:35, Jeff Courtade wrote:
> My concern with using g1 is solely based on finding this. Does
> anyone have any information on this?
>
> https://wiki.apache.org/lucene-java/JavaBugs#Oracle_Java_.2F_Sun_Java_
.2F_OpenJDK_Bugs
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 9/18/18 11:10, Christopher Schultz wrote:
> All,
>
> Our single-instance Solr server is just getting its first taste of
> production load, and I'm seeing this periodically:
>
> java.lang.IllegalStateException: C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dan,
On 9/18/18 2:51 PM, Dan Brown wrote:
> I've been working on this for a while and it's finally in a state
> where it's ready for public consumption.
>
> This is a command line indexer that will index CSV or JSON
> documents:
ake schema changes.)
Thanks,
- -chris
>> On Sep 18, 2018, at 8:15 AM, Christopher Schultz
>> wrote:
>>
> Walter,
>
> On 9/17/18 11:39, Walter Underwood wrote:
>>>> Do not use Solr as a database. It was never designed to be a
>>>> database.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Walter,
On 9/17/18 11:39, Walter Underwood wrote:
> Do not use Solr as a database. It was never designed to be a
> database. It is missing a lot of features that are normal in
> databases.
>
> [...] * no real backups (Solr backup is a cold server,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
Our single-instance Solr server is just getting its first taste of
production load, and I'm seeing this periodically:
java.lang.IllegalStateException: Connection is still allocated
The stack trace shows it's coming from HTTP Client as called
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 9/17/18 17:21, Shawn Heisey wrote:
> On 9/17/2018 3:01 PM, Christopher Schultz wrote:
>> The basic questions I'd like to have answered on a regular basis
>> are:
>>
>> 1. Is the JVM up (this can be don
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I can see three possibilities for monitoring a Solr (7.4.0) deployment:
1. bin/solr healthcheck
2. curl /solr/[collection]/admin/ping
3. JMX
Option #1 isn't available unless ZK is in use, and I'm not using ZK in
my case.
Option #2 issues a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jan,
On 9/16/18 16:22, Jan Høydahl wrote:
> We plan to enable (digest) authentication and ACL with Zookeeper to
> improve security.
Can you be more explicit? There is HTTP DIGEST auth and then there are
"digested" (hashed) passwords for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 9/12/18 12:21 PM, David Hastings wrote:
>> On Sep 12, 2018, at 12:15 PM, Christopher Schultz
>> mailto:ch...@christopherschultz.net>>
>> wrote:
>>
>> David,
>>
>> On 9/12/18 11:03 AM, D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 9/12/18 11:03 AM, David Hastings wrote:
> is there a way to start the default solr installation on more than
> one port? Only thing I could find was adding another connector to
> Jetty, via
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shalvak,
On 9/11/18 01:51, Shalvak Mittal (UST, ) wrote:
> I have recently installed solr 7.2.1 in my ubuntu 16.04 system.
> While creating a new core, the solr logging shows an error saying
>
>
> " Caused by:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 8/27/18 22:37, Shawn Heisey wrote:
> On 8/27/2018 8:29 PM, zhenyuan wei wrote:
>> I found the “solr.data.dir” can only config a single directory.
>> I think it is necessary to be config multi dirs，such as
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Adam,
On 8/20/18 1:45 PM, Adam Blank wrote:
> I'm running Solr 5.5.0 on AIX, and I'm wondering if there's a way
> to import the index from the command line instead of using the
> admin console? I don't have the ability to use a HTTP client such
>
Shawn,
On 8/16/18 10:37 AM, Shawn Heisey wrote:
> On 8/16/2018 7:48 AM, Christopher Schultz wrote:
>> I haven't actually tried this, yes, but from the docs I'm guessing that
>> I can't search for a DOB using e.g. 2018-08-16 but instead I need to
>> search using 2018-08-16T0
All,
My understanding is that Solr (really Lucene) only handles temporal data
using full timestamps (date+time, always UTC). I have a use-case where
I'd like to store and search for people by their birth dates, so the
timestamp information is not relevant for me.
I haven't actually tried this,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Erick,
On 8/15/18 12:56 PM, Erick Erickson wrote:
> Also note that the OpenJDK devs regularly get to test very early
> (unreleased) Java versions, which flushes out a lot of issues long
> before a general release of Java
We (dev@tomcat) get
or
user-wide certificate trust stores.
Is this certificate signed by a real CA, or are you building your own,
internal, private CA who is signing these certficates?
-chris
> -Original Message- From: Christopher Schultz
> Sent: Monday, August 13, 2018 12:00
> PM To: solr-user@luce
Kelly,
On 8/13/18 11:55 AM, Kelly Rusk wrote:
> I have imported a Wildcard Certificate to my Java Keystore and it
> displays, but when I pull up Internet Explorer and browse to my Solr
> site, it fails to load and presents TLS errors.
What do you mean "it displays"?
How did you import your
Ravion,
What's wrong with "update request"? Updating a document that does not
exist... will add it.
-chris
On 8/10/18 3:01 PM, ☼ R Nair wrote:
> Do you feel that this is only partially complete?
>
> Best, Ravion
>
> On Fri, Aug 10, 2018, 1:37 PM ☼ R Nair wrote:
>
>> I saw this. Please
Joe,
On 8/3/18 11:44 AM, Joe Lerner wrote:
> OK--yes, I can see how that would work. But it would require some quick
> infrastructure flexibility that, at least to this point, we don't really
> have.
The only thing that needs swapping is the URL that your application uses
to connect to Solr, so
Joe,
On 8/3/18 11:09 AM, Joe Lerner wrote:
> We recently set up Solr 7.4 in Production. There are 2 Solr nodes, with 3
> zookeepers. We need to make a schema change. What I want to do is simply
> push the updated schema to Solr, and then re-index all the content to pick
> up the change. But I am
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
To whom it may concern,
On 7/31/18 2:56 PM, tedsolr wrote:
> I'm having some trouble with non printable, but valid, UTF8 chars
> when exporting to Amazon Redshift. The export fails but I can't yet
> find this data in my Solr collection. How can I
e
> configured so that the server creates dumps ?
You don't want this to happen automatically. Instead, you'll want to
trigger a dump manually for debugging purposes.
- -chris
> Am 31.07.2018 um 15:07 schrieb Christopher Schultz: Georg,
>
> On 7/31/18 4:39 AM, Georg Fette wrote:
>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Georg,
On 7/31/18 4:39 AM, Georg Fette wrote:
> We run the server version 7.3.1. on a machine with 32GB RAM in a
> mode having -10g.
>
> When requesting a query with
>
> q={!boost
>
;8983"
I would expect your process to work. Did it?
- -chris
> -Original Message- From: Christopher Schultz
> Sent: Wednesday, July 25, 2018 3:23
> PM To: solr-user@lucene.apache.org Subject: Re: Upgrading SOLR (not
> clustered)
>
> Phil,
>
> On 7/25/18 12:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Phil,
On 7/25/18 12:38 PM, Staley, Phil R - DCF wrote:
> What are the steps for upgrading a non-clustered SOLR version?
> Here's what I thought should work:
>
>
>
> 1. Open a bash window and ssh login to desired server with
> your Linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 7/24/18 4:46 PM, Chris Hostetter wrote:
>
> : We are using Solr as a user index, and users have email
> addresses. : : Our old search behavior used a SQL substring match
> for any search : terms entered, and so users are used to being
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 7/24/18 1:40 PM, Chris Hostetter wrote:
>
> : So if I want to alias the "first_name" field to "first" and the :
> "last_name" field to "last", then I would ... do what, exactly?
>
> se the last example here...
>
>
mMap.put("defType", "edismax");
queryParamMap.put([??], "f.first.fq=first_name f.last.fq=last_name");
??
Thanks,
- -chris
>> On 5 Mar 2018, at 17:51, Christopher Schultz
>> wrote:
>>
> All,
>
> I'd like for users to be able to search a field by
t;
>> HTH, Emir -- Monitoring - Log Management - Alerting - Anomaly
>> Detection Solr & Elasticsearch Consulting Support Training -
>> http://sematext.com/
>>
>>
>>
>>> On 5 Mar 2018, at 17:51, Christopher Schultz
>> wrote:
>>>
> Al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
We are using Solr as a user index, and users have email addresses.
Our old search behavior used a SQL substring match for any search
terms entered, and so users are used to being able to search for e.g.
"chr" and finding my email address
Dinesh,
On 6/21/18 11:40 AM, Dinesh Sundaram wrote:
> is there any way to disable basic authentication for particular domain. i
> have proxy pass from a domain to solr which is always asking credentials so
> wanted to disable basic auth only for that domain. is there any way?
I wouldn't
Ratnadeep,
On 6/11/18 12:25 PM, Ratnadeep Rakshit wrote:
> I am using the Solr Suggester component in Solr 5.5 with a lot of address
> data. My Machine has allotted 20Gb RAM for solr and the machine has 32GB
> RAM in total.
>
> I have an address book core with the following vitals -
>
>
e.jks
>> set SOLR_SSL_TRUST_STORE=etc/solr-ssl.keystore.jks
>>
>> For your meaning of absolute paths actually start with a slash, meaning
>> we have to set it like this?
>>
>> set SOLR_SSL_KEY_STORE=/etc/solr-ssl.keystore.jks
>> set SOLR_SSL_TRUST_STORE=/etc/
Edwin,
On 6/8/18 12:02 PM, Zheng Lin Edwin Yeo wrote:
> I followed the steps from
> https://lucene.apache.org/solr/guide/7_3/enabling-ssl.html.
>
> 1)
>
> keytool -genkeypair -alias solr-ssl -keyalg RSA -keysize 2048 -keypass
> secret -storepass secret -validity -keystore
>
Edwin,
On 6/7/18 11:11 PM, Zheng Lin Edwin Yeo wrote:
> Hi,
>
> I am running SolrCloud on Solr 7.3.1 on External ZooKeeper 3.4.11, and I am
> setting up the security aspect of Solr.
>
> After setting up the SSL based on the steps from
>
TK
On 6/5/18 1:12 PM, TK Solr wrote:
> My client's Solr 6.6 running on a Windows server is mysteriously
> crashing without any JVM crash log. No unusual activities recorded in
> solr.log. GC log does not indicate the OOM situation. It's a simple
> single-core, single node deployment (no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kelly,
On 6/1/18 5:41 PM, Kelly Rusk wrote:
> I can directly connect to either node without issue, it is only
> when the Load Balancer routes to either solr1 or solr2 that I get
> the security error (ex. https://solrlb.com:8983/solr). The Load
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 6/1/18 5:25 PM, Shawn Heisey wrote:
> On 6/1/2018 2:01 PM, Kelly Rusk wrote:
>> We have solr1.com and solr2.com self-signed certs that correspond
>> to the two servers. We also have a load balancer with an address
>> named solrlb.com.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Roee,
On 5/30/18 3:38 AM, Roee T wrote:
> Thank you so much all of you the following worked for me!
>
> curl -X PUT -H "Content-Type: application/json" -d
> "@Myfeatures.json"
> "http://localhost:8983/solr/techproducts/schema/feature-store;
Curl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Roee,
On 5/29/18 11:02 AM, Roee Tarab wrote:
> I am having some troubles with pushing a features file to solr
> while building an LTR model. I'm trying to upload a JSON file on
> windows cmd executable from an already installed CURL folder, with
>
-24 09:05:17.153 INFO
> (coreLoadExecutor-7-thread-2-processing-n:9.109.122.113:8984_solr)
> [c:document r:core_node1 x:document] o.a.s.u.SolrIndexConfig
> IndexWriter infoStream solr logging is enabled [\] sleep: bad
> character in argument
What does the solr.log file say? The above stack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Anchal,
On 5/23/18 2:38 AM, Anchal Sharma2 wrote:
> Thank you for replying .But ,I checked the java version solr using
> ,and it is already version 1.8.
>
> @Christopher ,can you let me know what steps you followed for TLS
> authentication on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 5/17/18 4:23 AM, Shawn Heisey wrote:
> On 5/17/2018 1:53 AM, Anchal Sharma2 wrote:
>> We are using solr version 5.3.0 and have been trying to enable
>> security on our solr .We followed steps mentioned on site
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 4/24/18 11:23 AM, Shawn Heisey wrote:
> On 4/24/2018 8:50 AM, Steven White wrote:
>> Does anyone use Solr, any version, with OpenJDK? If so, what
>> has been you experience? Also, what platforms have you used it
>> on?
>
> I've used it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I have documents that need to appear to have different attributes
depending upon which user is trying to search them. One of the fields
I currently have in the document is called "latest_submission" and
it's a multi-valued text field that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 4/15/18 4:49 PM, Shawn Heisey wrote:
> On 4/15/2018 2:31 PM, Christopher Schultz wrote:
>> I'd usually call this a "date", but Solr's documentation says
>> that a "date" is what I would call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 4/15/18 4:33 PM, Shawn Heisey wrote:
> On 4/15/2018 2:24 PM, Christopher Schultz wrote:
>> No, it wouldn't have. It doesn't read any configuration files
>> and guesses its way through everything. Simply adding HTTPS
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I'd usually call this a "date", but Solr's documentation says that a
"date" is what I would call a timestamp (including time zone).
https://lucene.apache.org/solr/guide/7_3/field-types-included-with-solr.
html
[ I remember reading but cannot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 4/13/18 6:02 PM, Shawn Heisey wrote:
> On 4/13/2018 7:49 AM, Christopher Schultz wrote:
>> $
>> SOLR_POST_OPTS="-Djavax.net.ssl.trustStore=/etc/solr/solr-client.p12
>>
>>
- -Djavax.ne
All,
I've recently been encountering some frustrations with Solr 7.3 after
configuring TLS; since the command-line tools (which are a breeze to use
when you have a "toy" Solr installation) stop working when TLS is
enabled, I'm finding myself having to perform the following tasks in
order to get
Shawn,
On 4/10/18 10:16 AM, Shawn Heisey wrote:
> On 4/10/2018 7:32 AM, Christopher Schultz wrote:
>>> What happened is that the new core directory was created as root,
>>> owned by root.
>> Was it? If my server is running as solr, how can it create directories
>
Shawn,
On 4/9/18 8:04 PM, Shawn Heisey wrote:
> On 4/9/2018 12:58 PM, Christopher Schultz wrote:
>> After playing-around with a Solr 7.2.1 instance launched from the
>> extracted tarball, I decided to go ahead and create a "real service" on
>> my Debian-based s
All,
On 4/9/18 2:58 PM, Christopher Schultz wrote:
> All,
>
> After playing-around with a Solr 7.2.1 instance launched from the
> extracted tarball, I decided to go ahead and create a "real service" on
> my Debian-based server.
>
> I've run the 7.3.0 install
All,
After playing-around with a Solr 7.2.1 instance launched from the
extracted tarball, I decided to go ahead and create a "real service" on
my Debian-based server.
I've run the 7.3.0 install script, configured Solr for TLS, and moved my
existing configuration into the data directory, here:
$
Shawn,
On 3/20/18 9:13 AM, Shawn Heisey wrote:
> On 3/15/2018 6:40 AM, padmanabhan1616 wrote:
>> Hi Team,We are using Apache SOLR-5.2.1 as index engine for our data
>> analytics
>> application. As part of this SOLR uses commons-fileupload-1.2.1.jar
>> for file
>> manipulation.There is security
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mariano,
On 3/19/18 11:50 AM, LOPEZ-CORTES Mariano-ext wrote:
> Hello
>
> We have an index Solr with 3 nodes, 1 shard et 2 replicas.
>
> Our goal is to index 42 millions rows. Indexing time is important.
> The data source is an oracle database.
>
All,
I'm using Solr to index and search a database of user data (username,
email, first and last name), so there aren't really "terms" in the data
to search for, like you might search for words that describe products in
a catalog, for example.
I have set up my schema to include plain-old text
To whom it may concern,
On 3/15/18 8:40 AM, padmanabhan1616 wrote:
> Hi Team,We are using Apache SOLR-5.2.1 as index engine for our data analytics
> application. As part of this SOLR uses commons-fileupload-1.2.1.jar for file
> manipulation.There is security Vulnerability identified in
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Erick,
(Sorry... hit sent inadvertently before completion...)
On 3/12/18 2:50 PM, Erick Erickson wrote:
> Something like:
>
> solr/collection/query?q=chris shultz=edismax=all^10
> phonetic
Interesting. Looks like the "qf=all phonetic" would
be easier to understand.
>
> And I urge you to take it a little at a time, just use two fields
> and two terms and look at the result of =query, the parsed
> query bits, 'cause each new thing you add adds a further
> complication. Fortunately you can just put different paramet
:20 AM, Christopher Schultz
> <ch...@christopherschultz.net> wrote: All,
>
> I have a Solr index containing application user information
> (username, first/last, etc.). I have created an "all" field for the
> purpose of using it as a default. It contains most but not all
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I have a Solr index containing application user information (username,
first/last, etc.). I have created an "all" field for the purpose of
using it as a default. It contains most but not all fields.
I recently added phonetic searching for the
make it a
> practice to regularly pull it from ZK and put it in some VCS system
> ;)
Actually, I have the script that builds the schema in VCS, so it's
roughly the same.
As for the schema modifications... did I get those right?
Thanks,
- -chris
> On Mon, Mar 12, 2018 at 9:51 AM, Christophe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I'd like to add a new synthesized field that uses a phonetic analyzer
such as Beider-Morse. I'm using Solr 7.2.
When I request the current schema via the schema API, I get a list of
existing fields, dynamic fields, and analyzers, none of
e what happens :)
- -chris
> On 03/06/2018 04:20 PM, Christopher Schultz wrote:
>> Terry,
>>
>> On 3/6/18 4:08 PM, Terry Steichen wrote:
>>> Is it possible to run solr in a read-only directory?
>>
>>> I'm running it just fine on a ubuntu server wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Terry,
On 3/6/18 4:08 PM, Terry Steichen wrote:
> Is it possible to run solr in a read-only directory?
>
> I'm running it just fine on a ubuntu server which is accessible
> only through SSH tunneling. At the platform level, this is fine:
> only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I'd like for users to be able to search a field by multiple names
without performing a "copy-field" when analyzing a document. Is that
possible? Whenever I search for "solr alias field" I get results about
how to re-name fields in the results.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 3/2/18 7:46 PM, Shawn Heisey wrote:
> On 3/2/2018 10:39 AM, Christopher Schultz wrote:
>> The problem is that I'm updating the index after my SQL UPDATE(s)
>> have run, but before my SQL COMMIT occurs. I have had a p
Hey, folks. I've been a long-time Lucene user (running a hilariously-old
1.9.1 version forever), but I'm only just now getting into using Solr.
My particular use-case is storing information about web-application
users so they can be found more quickly than our current RDBMS-based
search (SELECT
98 matches
Mail list logo
