Live data from Hacker News

Major Changes from Solr 4 to Solr 5

cwiki.apache.org

1–10 of 47 posts

Re: Major Changes from Solr 4 to Solr 5

#3
Does Solr 5.0 support password-protecting the admin interface yet without spending hours trying to wrangle custom XML files? It seems like a pretty basic requirement for a web-based application.

I've tried things like this

http://community.zimbra.com/documentation/w/documentation/se...

repeatedly. They never seem to work right.

Re: Major Changes from Solr 4 to Solr 5

#5

Does Solr 5.0 support password-protecting the admin interface yet without spending hours trying to wrangle custom XML files? It seems like a pretty basic requirement for a web-based application. I've tried things like this http://community.zimbra.com/documentation/w/documentation/se... repeatedly. They never seem to work right.

Solr is not a web-based application. You shouldn't directly expose your Solr instance to anyone. Regardless of whether or not you secure your admin interface. That's not Solr's core business, and I don't see why they should was their efforts on it.

Have Solr listen on localhost and have your web app talk to Solr. If your Solr is visible to the world, you're doing it wrong.

Edit: by saying that it's not a web-based application I mean that it shouldn't be on teh interwebz -- it's obviously a webapp in the sense that it mostly speaks HTTP.

Re: Major Changes from Solr 4 to Solr 5

#7
post #6
post #4

Any reasons to prefer Solr over elastic-search?

Solr is backed by the Apache community while ES is backed by a private entity. Is that a good reason?

Not really, no. If ElasticsearchCo were to go belly-up, the technology would almost certainly be backed by someone else.

Re: Major Changes from Solr 4 to Solr 5

#8
post #5

Does Solr 5.0 support password-protecting the admin interface yet without spending hours trying to wrangle custom XML files? It seems like a pretty basic requirement for a web-based application. I've tried things like this http://community.zimbra.com/documentation/w/documentation/se... repeatedly. They never seem to work right.

Solr is not a web-based application. You shouldn't directly expose your Solr instance to anyone. Regardless of whether or not you secure your admin interface. That's not Solr's core business, and I don't see why they should was their efforts on it. Have Solr listen on localhost and have your web app talk to Solr. If your Solr is visible to the world, you're doing it wrong. Edit: by saying that it's not a web-based ap…

Well, regardless of whether it's web-facing or not, it's not unreasonable to want to limit the access to its admin panel (e.g. in a big company with different teams).

I agree however that SOLR is best off doing one thing well, web page security can be implemented e.g. by Apache.

Re: Major Changes from Solr 4 to Solr 5

#10
post #8
post #5

Earlier quoted context omitted.

Solr is not a web-based application. You shouldn't directly expose your Solr instance to anyone. Regardless of whether or not you secure your admin interface. That's not Solr's core business, and I don't see why they should was their efforts on it. Have Solr listen on localhost and have your web app talk to Solr. If your Solr is visible to the world, you're doing it wrong. Edit: by saying that it's not a web-based ap…

Well, regardless of whether it's web-facing or not, it's not unreasonable to want to limit the access to its admin panel (e.g. in a big company with different teams). I agree however that SOLR is best off doing one thing well, web page security can be implemented e.g. by Apache.

So limit it to only whitelisted IPs. That's why you have sysadmins.
Post reply on HN