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

Scripted metric should fail gracefully on unsupported return types #54665

Closed
not-napoleon opened this issue Apr 2, 2020 · 1 comment · Fixed by #54692
Closed

Scripted metric should fail gracefully on unsupported return types #54665

not-napoleon opened this issue Apr 2, 2020 · 1 comment · Fixed by #54692
Assignees

Comments

@not-napoleon
Copy link
Member

not-napoleon commented Apr 2, 2020

Scripted Metric aggregation running against an invalid return type can fail since it does not know how to serialize unknown types returned from scripts

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-analytics-geo (:Analytics/Aggregations)

@imotov imotov self-assigned this Apr 2, 2020
imotov added a commit to imotov/elasticsearch that referenced this issue Apr 2, 2020
Makes query result serialization more robust by propagating possible
IOExceptions that can occur during shard level result serialization to the
caller instead of throwing AssertError that is not intercepted.

Fixes elastic#54665
imotov added a commit that referenced this issue Apr 9, 2020
Makes query result serialization more robust by propagating possible
IOExceptions that can occur during shard level result serialization to the
caller instead of throwing AssertionError that is not intercepted.

Fixes #54665
imotov added a commit to imotov/elasticsearch that referenced this issue Apr 9, 2020
Makes query result serialization more robust by propagating possible
IOExceptions that can occur during shard level result serialization to the
caller instead of throwing AssertionError that is not intercepted.

Fixes elastic#54665
imotov added a commit to imotov/elasticsearch that referenced this issue Apr 9, 2020
Makes query result serialization more robust by propagating possible
IOExceptions that can occur during shard level result serialization to the
caller instead of throwing AssertionError that is not intercepted.

Fixes elastic#54665
imotov added a commit that referenced this issue Apr 10, 2020
Makes query result serialization more robust by propagating possible
IOExceptions that can occur during shard level result serialization to the
caller instead of throwing AssertionError that is not intercepted.

Fixes #54665
imotov added a commit that referenced this issue Apr 10, 2020
Makes query result serialization more robust by propagating possible
IOExceptions that can occur during shard level result serialization to the
caller instead of throwing AssertionError that is not intercepted.

Fixes #54665
yyff pushed a commit to yyff/elasticsearch that referenced this issue Apr 17, 2020
Makes query result serialization more robust by propagating possible
IOExceptions that can occur during shard level result serialization to the
caller instead of throwing AssertionError that is not intercepted.

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

Successfully merging a pull request may close this issue.

3 participants