[
https://issues.apache.org/jira/browse/SOLR-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229187#comment-14229187
]
Alexandre Rafalovitch commented on SOLR-4792:
---------------------------------------------
bq. ElasticSearch for that matter
The problem is that Solr ships as a kitchen sink while Elasticsearch ships as a
bare (production?) deployment. Just see the slides 4-5 of
http://www.slideshare.net/arafalov/solr-vs-elasticsearch-case-by-case . The
difference is stark.
So, with the war file, people would go and create various packages around
solr.war but without all the extra packages (e.g. Japanese, Polish, hadoop,
etc). Now, it is not clear what the - user - story for production deployment
will be now.
This is not a story that can be resolved JIRA by JIRA. It's a usability impact
that spans multiple issues and needs to be thought through on that level (this
JIRA is not even linked into higher-level item...). And the impact assessment
possibly includes looking at the things currently outside of Solr such as Linux
packages, Puppet deployment modules, etc. If this change breaks all of them
without any easy fix - the impact is quite high indeed.
But how and by whom this needs to be discussed? I have no idea. I am just doing
the _canary in the coal mine_ job righ tnow.
> stop shipping a war in 5.0
> --------------------------
>
> Key: SOLR-4792
> URL: https://issues.apache.org/jira/browse/SOLR-4792
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Assignee: Mark Miller
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-4792.patch
>
>
> see the vote on the developer list.
> This is the first step: if we stop shipping a war then we are free to do
> anything we want.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
