Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expose Lucenes KeepWordTokenFilter in ElasticSearch #2436

Closed
s1monw opened this issue Nov 22, 2012 · 1 comment
Closed

Expose Lucenes KeepWordTokenFilter in ElasticSearch #2436

s1monw opened this issue Nov 22, 2012 · 1 comment
Assignees
@s1monw
Labels
>enhancement v0.90.0.Beta1

Comments

@s1monw
Copy link
Contributor

s1monw commented Nov 22, 2012

Lucene 4 comes with a handy KeepWordTokenFilter that is basically an inverse stop filter. ES should expose this filter by default.
@ghost ghost assigned s1monw Nov 22, 2012
s1monw added a commit to s1monw/elasticsearch that referenced this issue Nov 22, 2012
@s1monw
elastic#2436 expose KeepWordTokenFilter by default
bc400df
s1monw added a commit that referenced this issue Nov 23, 2012
@s1monw
#2436 expose KeepWordTokenFilter by default
32a0772
@s1monw
Copy link
Contributor Author

s1monw commented Nov 23, 2012

pushed to master

@s1monw s1monw closed this as completed Nov 23, 2012
martijnvg added a commit that referenced this issue Apr 25, 2018
@martijnvg
ccr: Added maximum translog limit that a single shard changes respons…
a22a7d0 
…e can return.

This limit is based on the number of estimate bytes in each translog
operation that fall between the minimum and maximum request sequence number.

If this limit is met then the shard follow task executor will make sure
that a subsequent shard changes request will be performed to fetch the
remaining translog operations.

This limit is needed in order to protect against returning too many
translog operations in a single shard changes response.

Relates to #2436
martijnvg added a commit that referenced this issue Apr 25, 2018
@martijnvg
ccr: Added maximum translog limit that a single shard changes respons…
bbd8be0 
…e can return.

This limit is based on the number of estimate bytes in each translog
operation that fall between the minimum and maximum request sequence number.

If this limit is met then the shard follow task executor will make sure
that a subsequent shard changes request will be performed to fetch the
remaining translog operations.

This limit is needed in order to protect against returning too many
translog operations in a single shard changes response.

Relates to #2436
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@s1monw s1monw

Labels
>enhancement v0.90.0.Beta1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@s1monw