0
0
bleve/config
Marty Schoch e472b3e807 add support for a "web" tokenizer/analyzer
The goal of the "web" tokenizer is to recognize web things like
- email addresses
- URLs
- twitter @handles and #hashtags

This implementation uses regexp exceptions.  There will most
likely be endless debate about the regular expressions. These
were chosein as "good enough for now".

There is also a "web" analyzer.  This is just the "standard"
analyzer, but using the "web" tokenizer instead of the "unicode"
one.  NOTE: after processing the exceptions, it still falls back
to the standard "unicode" one.

For many users, you can simply set your mapping's default analyzer
to be "web".

closes #269
2015-11-30 14:27:18 -05:00
..
config_cld2.go major refactor of bleve configuration 2015-09-16 17:10:59 -04:00
config_cznicb.go major refactor of bleve configuration 2015-09-16 17:10:59 -04:00
config_forestdb.go major refactor of bleve configuration 2015-09-16 17:10:59 -04:00
config_icu.go major refactor of bleve configuration 2015-09-16 17:10:59 -04:00
config_kagome.go major refactor of bleve configuration 2015-09-16 17:10:59 -04:00
config_leveldb.go major refactor of bleve configuration 2015-09-16 17:10:59 -04:00
config_libstemmer.go major refactor of bleve configuration 2015-09-16 17:10:59 -04:00
config_rocksdb.go major refactor of bleve configuration 2015-09-16 17:10:59 -04:00
config.go add support for a "web" tokenizer/analyzer 2015-11-30 14:27:18 -05:00
README.md major refactor of bleve configuration 2015-09-16 17:10:59 -04:00

Bleve Config

NOTE you probably do not need this package. It is only intended for general purpose applications that want to include large parts of Bleve regardless of whether or not the code is directly using it.

General Purpose Applications

A general purpose application, that must allow users to express the need for Bleve components at runtime can accomplish this by:

import _ "github.com/blevesearch/bleve/config"