Re: Miserable Experience Using Solr. Again.

>> Good software doesn’t force users to learn how it works. It hides the inner workings under the interface, so that people never even have to worry about it at all. I agree - AND the fact is that the amount of effort involved in expressing (In a really well-made UI) every possible permutation of

Re: Miserable Experience Using Solr. Again.

> I would like to see a future where the admin UI is more than just an > addon ... but even then, I think the HTTP API will *still* be the most > important piece of the system. In 4 years of heavily using (many instances and many versions of) Solr, the only times when I've used the admin UI has be

Re: Miserable Experience Using Solr. Again.

On 16 September 2016 at 18:30, Stefan Matheis wrote: >> … choice between better docs and better UI, I’ll choose a better UI every >> time > > Aaron, you (as well as all others) are more than welcome to help out - no > matter what you do / how you do it. > > While we’d obviously would love to get

Re: Miserable Experience Using Solr. Again.

Responses inline. More potentially flimsy excuses coming your way. On 9/15/2016 9:56 PM, Aaron Greenspan wrote: > My two cents: I’m glad to see the discussion over improved documentation, but > if you give me a choice between better docs and better UI, I’ll choose a > better UI every time. If c

Re: Miserable Experience Using Solr. Again.

> … choice between better docs and better UI, I’ll choose a better UI every time Aaron, you (as well as all others) are more than welcome to help out - no matter what you do / how you do it. While we’d obviously would love to get some more hands helping out with the coding parts - improving the

Re: Miserable Experience Using Solr. Again.

Hi again, My two cents: I’m glad to see the discussion over improved documentation, but if you give me a choice between better docs and better UI, I’ll choose a better UI every time. If contributors are going to spend real time on the concerns raised in this thread, spend the time on making the

Re: Miserable Experience Using Solr. Again.

Just wanted to chime in on the technical set-up of the Solr "petting zoo", I think I can help here; just let me know what you need. Here is the idea; just have a vagrant box with ansible provisioning Zoo keepers and Solr, creating collections, and etc That way anyone starting out can just clon

Re: Miserable Experience Using Solr. Again.

On 9/15/2016 8:24 AM, Alexandre Rafalovitch wrote: > The WIKI may be an official community-contributing forum, but its > technological implementation has gotten so bad it is impossible to > update. Every time I change the page, it takes minutes (and feels like > hours) for the update to come throug

Re: Miserable Experience Using Solr. Again.

Maybe it's too much to manage without a corporate sponsor, as you say... But what about a cloneable AWS instance which people can then take responsibility for themselves? Or a set of VM's that could be downloaded? Or a Docker? I haven't done this so there may be roadblocks I'm unaware of - and I

Re: Miserable Experience Using Solr. Again.

On 15 September 2016 at 21:47, John Bickerstaff wrote: > One thing I'd like to suggest is that I believe the ideal tutorial does not > require someone to even install the software. Well, if somebody would just agree to run a hosted read-only instance of Solr we could totally do that by doing a tu

Re: Miserable Experience Using Solr. Again.

YES, YES, YES!!! I think nearly everyone on this list will agree that getting started with almost any open-source project is agony - it's just that we've all gotten used to sucking it up and getting past it. Solr, given it's many moving parts and multiple ways of doing things is "worse" than

Re: Miserable Experience Using Solr. Again.

The WIKI may be an official community-contributing forum, but its technological implementation has gotten so bad it is impossible to update. Every time I change the page, it takes minutes (and feels like hours) for the update to come through. No clue what to do about that though. Creating the shor

Re: Miserable Experience Using Solr. Again.

hey On 09/15/16 04:35, Jan Høydahl wrote: and the official user-contributed docs is at http://wiki.apache.org/solr/ But I wonder if we should consider creating an official, slim Solr User Guide as well, for end users, structured as a getting-started guide and with

Re: Miserable Experience Using Solr. Again.

On 9/15/2016 2:35 AM, Jan Høydahl wrote: > But I wonder if we should consider creating an official, slim Solr > User Guide as well, for end users, structured as a getting-started > guide and with focus on how you achieve a task, not documenting all 99 > parameters a plugin can take. Yes, I like t

Re: Miserable Experience Using Solr. Again.

I was not proposing StackOverflow as some official docs. Solr’s only official doc is the RefGuide, and the official user-contributed docs is at http://wiki.apache.org/solr/ But it may be that some of you Solr users want to contribute to StackOverflow’s Solr topic, bo

Re: Miserable Experience Using Solr. Again.

While stack overflow is a great place, and the more good info that exists there, the merrier, I think Solr should have it's own complete docs, in addition to anything found on 3rd party sites. Each hop to a new location is a chance for the user to get lost, and the content on 3rd party sites could

Re: Miserable Experience Using Solr. Again.

> If you could decide, what kind of documentation would you want from the > project? A very short “Solr Quick start guide”? with step-by-step > instructions for the most common tasks from a User perspective? I just became aware of StackOverflow’s Documentation project, which also has a solr top

Re: Miserable Experience Using Solr. Again.

On 9/13/2016 5:42 PM, Aaron Greenspan wrote: > I get this on digest mode (and wasn’t even sure my initial message > went through to the list), so please forgive the delay in responding. I've added you as BCC so you'll get this as soon as I send it. I wrote most of it last night, and left it to c

Re: Miserable Experience Using Solr. Again.

> 14. sep. 2016 kl. 01.42 skrev Aaron Greenspan : First of all, thanks for spending some time to give feedback and opening JIRAs (even if some get closed because it is a question, not a bug report). This list is exactly the right forum to bring up frustrations newbie users might have with Solr,

Re: Miserable Experience Using Solr. Again.

On 14 September 2016 at 06:42, Aaron Greenspan wrote: > This is a potential solution, but not one I choose to pursue. For one thing, > I am not an idiot. I’ve managed Linux systems for about 18 years now and I’ve > been programming for 20. I have learned that I am rarely the best at > anything,

Re: Miserable Experience Using Solr. Again.

Hello again… I get this on digest mode (and wasn’t even sure my initial message went through to the list), so please forgive the delay in responding. I think the various reactions to my post suggest that a sizable number of users (and by "users" I mean those who are not affiliated with Apache a

Re: Miserable Experience Using Solr. Again.

On 9/12/2016 3:48 PM, Aaron Greenspan wrote: > I have been on this list for some time because I know that any time I > try to do anything related to Solr I’m going to have to spend hours on > it, wondering why everything has to be so awful, and I just want > somewhere to provide feedback with the d

Re: Miserable Experience Using Solr. Again.

On 13 September 2016 at 16:46, Alessandro Benedetti wrote: >> It didn’t say which field type. Buried in the logs I found a reference in >> the Java stack trace—which *disappears* (and distorts the viewing window >> horribly) after a few seconds when you try to view it in the web log UI—to >> the

Re: Miserable Experience Using Solr. Again.

I stuck in 5.3.1 because if upgrade to 5.5 or 6.x my cluster dies. Doing a rolling upgrade, when I upgrade the second node to 5.5 both die in the per-sync phase, I don't know what changes in 5.5 but it's demanding a huge quantity of memory to check if the replica it's in sync. This kind o

Re: Miserable Experience Using Solr. Again.

First of all I second Bram, I am sorry you had a bad experience with Solr, but I think that: - without a minimum study and documentation - without trying to follow the best practices I think you are going to have a "miserable" experience with any software, don't you ? In addition to Bram : On Mo

Re: Miserable Experience Using Solr. Again.

I'm sorry you're having a "miserable" experience "again". That's certainly not my experience with Solr. That being said: > First I was getting errors about "Unsupported major.minor version 52.0", so I > needed to install the Linux x64 JRE 1.8.0, which I managed on CentOS 6 with... > yum install o

Re: Miserable Experience Using Solr. Again.

Sure - ping me off the list and I'll send my text file docs. They're rough and (of course) focused on what I'm doing, but they just might relieve some of the pain. Caveat - all on Linux and command line - no Admin UI api's -- I like the feel of the command line so I use it. On Mon, Sep 12, 2016

Re: Miserable Experience Using Solr. Again.

Interested for sure Bill Bell Sent from mobile > On Sep 12, 2016, at 4:05 PM, John Bickerstaff > wrote: > > For what it's worth - I found enough frustration upgrading that I decided > to "upgrade by replacement" > > Now, I suppose if you've got a huge dataset to re-index that could be a > pr

Re: Miserable Experience Using Solr. Again.

I would also add that dealing with Java versions has always been a pain until you get used to the whole "JAVA HOME" thing, but that this isn't anything to do with SOLR per se - it's just part and parcel of dealing with open source software that uses Java... Big changes between major versions of an

Re: Miserable Experience Using Solr. Again.

For what it's worth - I found enough frustration upgrading that I decided to "upgrade by replacement" Now, I suppose if you've got a huge dataset to re-index that could be a problem, but just in case an option like that helps you, I'll suggest this. 1. Install 6.x on a new machine using the "inst