Skip to content

Actions: elastic/elasticsearch-net

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
167 workflow run results
167 workflow run results

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Sub-Aggregate Not Deserializing Ingest Issue #794: Issue #8359 opened by deinman
27s
27s
Sub-Aggregate Not Deserializing Ingest Issue #793: Issue #8359 labeled by deinman
15s
15s
Sub-Aggregate Not Deserializing Ingest Issue #792: Issue #8359 labeled by deinman
3s
3s
Close stale issues Close stale issues #50: Scheduled
10s main
main
10s
Usability improvements (meta issue) Ingest Issue #791: Issue #8356 edited by flobernd
13s
13s
PropertyNamingPolicy from JsonSerializerOptions of the DefaultSourceSerializer is not applied for mappings Ingest Issue #790: Issue #8357 labeled by flobernd
13s
13s
Fluent configuration of Remove processor on PutPipelineRequestDescriptor doesn't support field descriptor Ingest Issue #789: Issue #8358 labeled by flobernd
14s
14s
Fluent configuration of Remove processor on PutPipelineRequestDescriptor doesn't support field descriptor Ingest Issue #788: Issue #8358 labeled by flobernd
19s
19s
Fluent configuration of Remove processor on PutPipelineRequestDescriptor doesn't support field descriptor Ingest Issue #787: Issue #8358 labeled by flobernd
33s
33s
Fluent configuration of Remove processor on PutPipelineRequestDescriptor doesn't support field descriptor Ingest Issue #786: Issue #8358 opened by stevejgordon
36s
36s
Fluent configuration of Remove processor on PutPipelineRequestDescriptor doesn't support field descriptor Ingest Issue #785: Issue #8358 labeled by stevejgordon
19s
19s
PropertyNamingPolicy from JsonSerializerOptions of the DefaultSourceSerializer is not applied for mappings Ingest Issue #784: Issue #8357 labeled by flobernd
15s
15s
PropertyNamingPolicy from JsonSerializerOptions of the DefaultSourceSerializer is not applied for mappings Ingest Issue #783: Issue #8357 edited by stevejgordon
14s
14s
PropertyNamingPolicy from JsonSerializerOptions of the DefaultSourceSerializer is not applied for mappings Ingest Issue #782: Issue #8357 labeled by stevejgordon
29s
29s
PropertyNamingPolicy from JsonSerializerOptions of the DefaultSourceSerializer is not applied for mappings Ingest Issue #781: Issue #8357 opened by stevejgordon
3s
3s
PropertyNamingPolicy from JsonSerializerOptions of the DefaultSourceSerializer is not applied for mappings Ingest Issue #780: Issue #8357 labeled by stevejgordon
15s
15s
Close stale issues Close stale issues #49: Scheduled
10s main
main
10s
Close stale issues Close stale issues #48: Scheduled
15s main
main
15s
Usability improvements (meta issue) Ingest Issue #779: Issue #8356 edited by flobernd
17s
17s
Make it possible to do a MultiSearch with different types Ingest Issue #778: Issue #8355 labeled by flobernd
27s
27s
Make it possible to do a MultiSearch with different types Ingest Issue #777: Issue #8355 labeled by flobernd
15s
15s
illegal_argument_exception when calling the Field Capabilities API Ingest Issue #776: Issue #8354 labeled by flobernd
19s
19s
SearchResponse and ScrollResponse do not have a common base class Ingest Issue #775: Issue #8353 unlabeled by flobernd
14s
14s
SearchResponse and ScrollResponse do not have a common base class Ingest Issue #774: Issue #8353 unlabeled by flobernd
25s
25s
SearchResponse and ScrollResponse do not have a common base class Ingest Issue #771: Issue #8353 labeled by flobernd
2s
2s