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

excludeFields parameter in river. #76

Closed
richardwilly98 opened this issue May 13, 2013 · 3 comments
Closed

excludeFields parameter in river. #76

richardwilly98 opened this issue May 13, 2013 · 3 comments

Comments

@richardwilly98
Copy link
Owner

This parameter should provide a comma separated list of fields that should not be indexed.

Currently the only option available to exclude fields to be indexed is using a script filter. It would be probably more efficient to exclude directly within the river.

Please rate this feature.

richardwilly98 added a commit that referenced this issue May 18, 2013
- Implement exclude fields feature using exclude_fields in options
attribute.
- Example:
"options": {
"exclude_fields": ["exclude-field-1", "exclude-field-2"]
},
@richardwilly98
Copy link
Owner Author

Add support for child level attributes using dotted notation.
exclude_fields = ["level1.level2"]

{
    "level1" : {
        "level2" : {
            "attribute" : "1"
        },
        "attribute2" : "9"
    }
}   

Should be transformed in

{
    "level1" : {
        "attribute2" : "9"
    }
}

richardwilly98 added a commit that referenced this issue Jun 11, 2013
- Add support for filtering nested objects
@agarwal-karan
Copy link

using include_fields as a parameter in options. however there are other extra keys that are getting indexed. Any pointers ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants