What is the best solution for filtering out Elasticsearch results with hate words? -


i want filter out docs hate words in ealsticsearch result. having bool filter in every search query list of words. , results in tons of slow queries, since list of hate words long (so of hatred around :( )

i wondering best practices spam/hate words filtering.

here considering:

  1. pre-process : scan doc prior indexing , hence mark them bad or not index them. problem : documents indexed several processes , difficult force rule on new component 1 writes.

  2. creating percolator , running periodically (not sure of best frequency , timing) tag documents bad words "baddoc" : true. hence have filter in queries. problem: not sure of performance impact due periodical running of percolator, secondly same problem of discipline in queries exclude baddoc

personally favor pure es solution , sure not new problem, , hence seeking expert guidance , best practices.

thanks , regards varun

using percolator tag bad document need define percolator include search criteria of "hate words".

one possible solution without percolator defining synonym list(if not using already) or extending existing synonym file in analyzer. can define synonym "hate words" gets replaced single term "badbaddocument". during query can filter out bad documents using simple boolean filter containing single term.


Comments

Post a Comment

Popular posts from this blog

java - Spring Data JPA: Why findOne(id) executing delete query internally? -

i have 1 application using @manytomany annotation link 2 different entities 1 parent entity. not sure if have implemented properly. when execute .findone() on parent entity's repository find it, @ first fetch data along executing delete queries internally delete record mapping table (a table jpa creates after adding @manytomany annotation.). following generated sql queries , code snippet: java class @entity @table(name = "inventory") public class inventory { @id long id; // many other properties @manytomany(fetch=fetchtype.lazy) private list<stream> streams; @manytomany(fetch=fetchtype.lazy) private list<subject> subjects; } there no other annotation i've put in stream , subject entity class link inventory class. when run app, create following tables: inventory stream subject inventory_stream inventory_subject (inventory_stream , inventory_subject, 2 tables created automatically, don't k...
Read more

python - Mongodb How to add addtional information when aggregating? -

i beginner , wrote line pipeline works, wanna add other information output, screen name , or number of tweets.i tried add under $group gave me syntax error everytime here pipeline: def make_pipeline(): # complete aggregation pipeline pipeline = [ { '$match': { "user.statuses_count": {"$gt":99 }, "user.time_zone": "brasilia" } }, { "$group": { "_id": "$user.id", "followers": { "$max": "$user.followers_count" } } }, { "$sort": { "followers": -1 } }, { "$limit" : 1 } ]; i using on example : { "_id" : objectid("5304e2e3cc9e684aa98bef97"), "text" : "first week of school on :p", "in_reply_to_status_id" : null, "retweet_count" : null, ...
Read more

java - Incorrect order of records in M-M relationship in hibernate -

Image
i have 4 records in bridge table in mysql database. using @manytomany in hibernate, accurate order of employees incorrect incorrect of projects. following required material figure out doing mistake. this source. @entity @table(name="project") public class projectbean { @id @generatedvalue @column(name="project_id") private int projectid; @column(name="title") private string projecttitle; @manytomany(mappedby="projects") private collection<employeebean> employees; public projectbean() { employees = new arraylist<employeebean>(); } //getters & setters } @entity @table(name="employee") public class employeebean { @id @generatedvalue @column(name="employee_id") private int employee_id; @column(name="first_name") private string ...
Read more