@@ -100,6 +100,8 @@ data EsScribeCfg = EsScribeCfg {
100100-- * Pool size of 2
101101--
102102-- * Annotate types set to False
103+--
104+-- * NoIndexSharding
103105defaultEsScribeCfg :: EsScribeCfg
104106defaultEsScribeCfg = EsScribeCfg {
105107 essManagerSettings = defaultManagerSettings
@@ -125,21 +127,24 @@ defaultEsScribeCfg = EsScribeCfg {
125127-- EveryMinuteIndexSharding will generate indexes based on the time of
126128-- the log. Index name is treated as a prefix. So if your index name
127129-- is @foo@ and DailySharding is used, logs will be stored in
128−-- @foo-2016-02-25@, @foo-2016-02-26@ and so on. Index templating will
130+-- @foo-2016-2-25@, @foo-2016-2-26@ and so on. Index templating will
129131-- be used to set up mappings automatically. Deletes based on date are
130132-- very fast and queries can be restricted to date ranges for better
131133-- performance. Queries against all dates should use @foo-*@ as an
132134-- index name. Note that index aliasing's glob feature is not suitable
133135-- for these date ranges as it matches index names as they are
134136-- declared, so new dates will be excluded. DailyIndexSharding is a
135−-- reasonable choice. Changing index sharding strategies is a *bad
136−-- idea*.
137+-- reasonable choice. Changing index sharding strategies is not
138+-- advisable.
137139--
138140-- * CustomSharding: supply your own function that decomposes an item
139141-- into its index name heirarchy which will be appended to the index
140142-- name. So for instance if your function return ["arbitrary",
141143-- "prefix"], the index will be @foo-arbitrary-prefix@ and the index
142−-- template will be set to match @foo-*@
144+-- template will be set to match @foo-*@. In general, you want to use
145+-- segments of increasing granularity (like year, month, day for
146+-- dates). This makes it easier to address groups of indexes
147+-- (e.g. @foo-2016-*@).
143148data IndexShardingPolicy = NoIndexSharding
144149 | MonthlyIndexSharding
145150 | DailyIndexSharding