Extension that can be used to perform operations with Elastic Search
APACHE-2.0 License
Bot releases are visible (Hide)
Published by AnuGayan over 2 years ago
Full Changelog: https://github.com/siddhi-io/siddhi-store-elasticsearch/compare/v3.2.1...v3.2.2
Published by dnwick over 2 years ago
Published by mohanvive almost 5 years ago
This Release is compatible with Siddhi 5.x.x
Siddhi Store Elasticsearch 3.2.0 release introduces support to add custom JSON documents into elasticsearch indexes
@sink(type = 'elasticsearch', host = '172.17.0.2', port = '9200',
index.name = 'stock_index',
@map(type = 'json',
@payload(""" {
"StockData":{
"Symbol":"{{symbol}}",
"Price":{{price}},
"Volume":{{volume}}
}
} """)))
define stream stock_stream(symbol string, price float, volume long);
Please find the complete changes here
Download the release from here
Published by mohanvive about 5 years ago
This Release is compatible with Siddhi 5.x.x
Siddhi Store Elasticsearch 3.1.2 release contains bug fixes, documentation updates and Siddhi dependency upgrade to 5.1.5.
Please find the complete changes here
Download the release from here
Published by mohanvive about 5 years ago
This Release is compatible with Siddhi 5.x.x
Siddhi Store Elasticsearch 3.1.1 release contains improvements related to backoff retry logic.
No Bug Fixes
Please find the complete changes here
Download the release from here
Published by dilini-muthumala about 5 years ago
This Release is compatible with Siddhi 5.x.x
Siddhi Store Elasticsearch 3.1.0 release contains some improvements related to type mapping support and bug fixes.
@Store(type="elasticsearch", @TypeMappings(requestTimestamp="date", latitude="geo_point", longitude="geo_point"), elasticsearch.member.list="http://localhost:9200",username="elastic", password="changeme", bulk.actions="10000", bulk.size="5")
define table ESTable (meta_clientType string, requestTimestamp long, latitude double, longitude double);
Here we can specify the list of type mappings.
In this example config, 'requestTimestamp' attribute is mapped to type 'date', 'latitude' attribute is being mapped to type 'geo_point' and so on.
Note:
If above annotation is used then need to re-index all the existing data after updating the mapping type. Otherwise we would see the following warning in Kibana when we try to update the index pattern.
"Mapping conflict . A field is defined as several types (string, integer, etc) across the indices that match this pattern. You may still be able to use these conflict fields in parts of Kibana, but they will be unavailable for functions that require Kibana to know their type. Correcting this issue will require reindexing your data."
createIndex()
method fails with ElasticsearchStatusException
(#23)Please find the complete changes here
Published by dnwick over 5 years ago
In this release introduces a new annotation called TypeMappings. Please refer example config below:
@Store(type="elasticsearch", @TypeMappings(requestTimestamp="date", latitude="geo_point", longitude="geo_point"), elasticsearch.member.list="http://localhost:9200",username="elastic", password="changeme", bulk.actions="10000", bulk.size="5")
define table ESTable (meta_clientType string, requestTimestamp long, latitude double, longitude double);
Here we can specify the list of type mappings.
In this example config, 'requestTimestamp' attribute is mapped to type 'date', 'latitude' attribute is being mapped to type 'geo_point' and so on.
Note:
If above annotation is used then need to re-index all the existing data after updating the mapping type. Otherwise we would see the following warning in Kibana when we try to update the index pattern.
"Mapping conflict . A field is defined as several types (string, integer, etc) across the indices that match this pattern. You may still be able to use these conflict fields in parts of Kibana, but they will be unavailable for functions that require Kibana to know their type. Correcting this issue will require reindexing your data."