What would be the "best" way to strip hyperlinks (eg. http://google.com, www.facebook.com, etc.) and avoid them being analyzed? So far I've been
using the pattern_replace char filter with reasonable success, but the
regex is getting quite big/complex to handle all the edge cases and even
tho we're still experimenting with ES, I'm starting to worry about the
performance impact of doing this when we start to ingest large volumes of
data into our ES cluster. Would the pattern_replace token filter be a
better option here?
I do all my HTML munging in the application that sends data to
Elasticsearch. I know that isn't much help, but it does work.
On Tue, Oct 7, 2014 at 5:03 PM, Hermano Cabral <
hermanocabral@creactive.com.br> wrote:
Howdy,
What would be the "best" way to strip hyperlinks (eg. http://google.com, www.facebook.com, etc.) and avoid them being analyzed? So far I've been
using the pattern_replace char filter with reasonable success, but the
regex is getting quite big/complex to handle all the edge cases and even
tho we're still experimenting with ES, I'm starting to worry about the
performance impact of doing this when we start to ingest large volumes of
data into our ES cluster. Would the pattern_replace token filter be a
better option here?
Yeah, thanks for the idea but unfortunately that's not really an option for
me as I have no control over how the data gets sent to ES.
On Tue, Oct 7, 2014 at 6:05 PM, Nikolas Everett nik9000@gmail.com wrote:
I do all my HTML munging in the application that sends data to
Elasticsearch. I know that isn't much help, but it does work.
On Tue, Oct 7, 2014 at 5:03 PM, Hermano Cabral <
hermanocabral@creactive.com.br> wrote:
Howdy,
What would be the "best" way to strip hyperlinks (eg. http://google.com, www.facebook.com, etc.) and avoid them being analyzed? So far I've been
using the pattern_replace char filter with reasonable success, but the
regex is getting quite big/complex to handle all the edge cases and even
tho we're still experimenting with ES, I'm starting to worry about the
performance impact of doing this when we start to ingest large volumes of
data into our ES cluster. Would the pattern_replace token filter be a
better option here?
On Tue, Oct 7, 2014 at 6:48 PM, Hermano Cabral <
hermanocabral@creactive.com.br> wrote:
Yeah, thanks for the idea but unfortunately that's not really an option
for me as I have no control over how the data gets sent to ES.
On Tue, Oct 7, 2014 at 6:05 PM, Nikolas Everett nik9000@gmail.com wrote:
I do all my HTML munging in the application that sends data to
Elasticsearch. I know that isn't much help, but it does work.
On Tue, Oct 7, 2014 at 5:03 PM, Hermano Cabral <
hermanocabral@creactive.com.br> wrote:
Howdy,
What would be the "best" way to strip hyperlinks (eg. http://google.com, www.facebook.com, etc.) and avoid them being analyzed? So far I've been
using the pattern_replace char filter with reasonable success, but
the regex is getting quite big/complex to handle all the edge cases and
even tho we're still experimenting with ES, I'm starting to worry about the
performance impact of doing this when we start to ingest large volumes of
data into our ES cluster. Would the pattern_replace token filter be
a better option here?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.