[
https://issues.apache.org/jira/browse/SOLR-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587494#comment-13587494
]
Mark Miller commented on SOLR-3843:
-----------------------------------
Your talking about something completely different - I'm talking about adding
300k to a webapp - sounds like you want to file a different JIRA issue that has
little to do with that.
In the modern day, I have no problem with the Solr dist - I'd much rather get
everything simply as we do than have to stitch crap together. I have disk space
and bandwidth as does the majority of the modern world now. If you are offering
to write a package manager for solr for unix/windows/mac, please go ahead :)
But until then, it makes no sense to not include the codecs the same way we do
with analyzers and spellchecker and highlighter, and whatever else we need.
If I had to run 10 commands to get solr, get spellchecking, get analyzers, get
highlighing, get QueryParsers, get MoreLikeThis, etc, I would shoot myself.
> Add lucene-codecs to Solr libs?
> -------------------------------
>
> Key: SOLR-3843
> URL: https://issues.apache.org/jira/browse/SOLR-3843
> Project: Solr
> Issue Type: Wish
> Affects Versions: 4.0
> Reporter: Adrien Grand
> Priority: Critical
> Fix For: 4.2, 5.0
>
> Attachments: SOLR-3843.patch, SOLR-3843.patch, SOLR-3843.patch
>
>
> Solr gives the ability to its users to select the postings format to use on a
> per-field basis but only Lucene40PostingsFormat is available by default
> (unless users add lucene-codecs to the Solr lib directory). Maybe we should
> add lucene-codecs to Solr libs (I mean in the WAR file) so that people can
> try our non-default postings formats with minimum effort?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
