I use XMLStarlet. We will also discuss any useful tools at the SolrERG
(original subject of the thread)
Regards,
Alex
On 10 Oct 2016 4:15 AM, wrote:
> Rick Leir said:> I commonly do a diff of the xmls to see what has changed
> in a new
> > release, or what differs in an example. The in
Rick Leir said:> I commonly do a diff of the xmls to see what has changed in a
new
> release, or what differs in an example. The indentation is often
> 'tidied up' in different ways, making the diff almost useless. Perhaps I
> need to run an xml formatter before doing any diff's on xml's. Als
Personally I'd like an XML formatter as part of the checkin process ;)...
But that's not my point. In any "replace configs" discussion, we need to be
aware of the many different environments that are out there "in the wild".
An indentation-sensitive format like YAML brings with it its own problems
On 2016-10-07 01:04 PM, Erick Erickson wrote:
Rick:
..
I've seen a _lot_ of configs in the wild with weird indentation, they
tend to get that way because there are lots of situations I've seen
where people edit them through some kind of remote terminal and can
only edit in some vi-like editor.
Rick:
It'll be an uphill battle to change the configs I think.. That said
there are no plans to go in that direction, but it's certainly a valid
discussion to have.
I've seen a _lot_ of configs in the wild with weird indentation, they
tend to get that way because there are lots of situations I've
The current direction is JSON. So yeah, I don't think YAML discussion
will get very far.
The problem with examples is that they also serve as documentation and
as a master source for configuration snippets (e.g. language-specific
types). Changing that is happening in several different JIRAs, but i
Thanks for using the word bewildering, I agree.
While we are talking of simplifying solrconfig.xml, may I mention YAML?
I find the YAML format so much more readable than XML.
I have not looked at the code which reads the config, so I do not know
how big a change it is to use cfg4j and read
Yeah, I agree actually. That was an experiment in the radical
simplification. I'll have uniqueKey, and _version_ back. But the fact
that the schema still works is a good teaching point, in my mind.
At the same time, I am still struggling with the reasonable minimal
solrconfig.xml. None of the ship
I'm a little reluctant to remove id and _version_ as they're
so essential to SolrCloud. Stand alone for that matter, I
strongly recommend that people have a
no matter what as the "usual" expectation is to replace docs
I think...
But perhaps a minimal_config and milnimal_cloud_config?
In either c
http://gethue.com/ does Solr as part of Big Data, but not sure about Nutch
https://github.com/DigitalPebble/behemoth has Solr and Nutch, but not
sure about UI
LucidWorks' commercial Fusion platform I believe has both with UI
Solr default config has LOTS of comments :-) Of course, the ones in
manag
On Wed, Oct 5, 2016 at 11:15 AM, Alexandre Rafalovitch
wrote:
> I have an nearly minimal config for Solr 4.9, 5.5 and 6.2 at:
> https://github.com/arafalov/simplest-solr-config/ . They are _quite_
> feature minimal (6.2 does not even have ID or version), but they will
> import and search example/e
I have an nearly minimal config for Solr 4.9, 5.5 and 6.2 at:
https://github.com/arafalov/simplest-solr-config/ . They are _quite_
feature minimal (6.2 does not even have ID or version), but they will
import and search example/exampledocs/*.xml without fuss
I challenge you to guess number of lines
Charlie:
I like that idea. It's bewildering how much stuff is in the config. I
do think there's value in having it all there though since people
won't even know to look in, say, "kitchen-sink-solrconfig.xml" for all
the _other_ things that can be done
Perhaps comment out all the "extra stuff"
On 05/10/2016 02:19, Walter Underwood wrote:
I’m trying to bring up 6.2.1 after experience with 1.2 through 5.5, and it is a
mess.
I’ve done solid good practice (Zookeeper ensemble, chroot, data on EBS volume),
but I’m stuck with a completely non-instructive stack trace.
We run a separate data
I’m trying to bring up 6.2.1 after experience with 1.2 through 5.5, and it is a
mess.
I’ve done solid good practice (Zookeeper ensemble, chroot, data on EBS volume),
but I’m stuck with a completely non-instructive stack trace.
We run a separate data directory and SOLR_HOME, which is poorly suppor
Hello,
Three weeks ago I asked this list whether there was an interest in
running a virtual examples reading group, with "all questions
welcome". The response was sufficient to start planning the first
study group.
The current projected date is start of November. You can register for
it at: https
16 matches
Mail list logo
