I'm not sure about lang files. I added it because we have a lot of
language-specific field types defined in our `schema.xml` and I tried to reuse
old schema as much as posible.
For example:
~~~~~
<!-- Russian -->
<fieldType name="text_ru" class="solr.TextField" positionIncrementGap="100">
<analyzer>
<tokenizer class="solr.StandardTokenizerFactory"/>
<filter class="solr.LowerCaseFilterFactory"/>
<filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_ru.txt" format="snowball" />
<filter class="solr.SnowballPorterFilterFactory" language="Russian"/>
<!-- less aggressive: <filter
class="solr.RussianLightStemFilterFactory"/> -->
</analyzer>
</fieldType>
~~~~~
I'm not sure if we're using them somewhere... Just checked now. In `schema.xml`
we're using only `text_general` and `text_ws`, so I'll try to get rid of others
and delete lang files.
I'll fix warning and chmod too. I used older docker back then, so didn't see
that.
---
** [tickets:#7907] Use standardized solr installation**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** sf-4 sf-current 42cc
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Tue Dec 08, 2015 11:04 PM UTC
**Owner:** Igor Bondarenko
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set
up. For the step-by-step we should use system packages and perhaps borrow
ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed
to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
