I want to use Elasticsearch or only indexing and searching E-Mails. We want
to store the meta-info within Elasticsearch, keeping the content/body of
every Mail in an mySQL database. So Elasticsearch shall have a reference to
the mail body.
I want to use Elasticsearch or only indexing and searching E-Mails. We
want to store the meta-info within Elasticsearch, keeping the content/body
of every Mail in an mySQL database. So Elasticsearch shall have a reference
to the mail body.
Using this plugin would lead to a migration from mysql data into
Elasticsearch.
So let me reformulate my question:
My infrastructure is like this:
client---->Elasticsearch
|
|
-------->mySQL
So I have a client which generates an index and some metadata for a
mail(header and body). The mail is stored in mySQL. And the client-side
generated index and metadata is stored in Elasticsearch.
The reason is because I have > 1 TB of mail content every day. This content
shall still be written to mySQL. Elasticsearch shall keep only the index.
Is that possible? And how?
I want to use Elasticsearch or only indexing and searching E-Mails. We
want to store the meta-info within Elasticsearch, keeping the content/body
of every Mail in an mySQL database. So Elasticsearch shall have a reference
to the mail body.
What I don't understand is why you generate an index and want to store it
in elasticsearch. You could use the plugin as Jörg suggested, transfer you
data to elasticsearch, set index:true for the fields you want and set
store:false in the mapping. This way you get an index build by
elasticsearch, can search on it, get the id as result and the data is not
stored (except metadata, if you set it to be stored). See Elasticsearch Platform — Find real-time answers at scale | Elastic.
Using this plugin would lead to a migration from mysql data into
Elasticsearch.
So let me reformulate my question:
My infrastructure is like this:
client---->Elasticsearch
|
|
-------->mySQL
So I have a client which generates an index and some metadata for a
mail(header and body). The mail is stored in mySQL. And the client-side
generated index and metadata is stored in Elasticsearch.
The reason is because I have > 1 TB of mail content every day. This
content shall still be written to mySQL. Elasticsearch shall keep only the
index. Is that possible? And how?
I want to use Elasticsearch or only indexing and searching E-Mails. We
want to store the meta-info within Elasticsearch, keeping the content/body
of every Mail in an mySQL database. So Elasticsearch shall have a reference
to the mail body.
It can be configured to select the data from the RDBMS you want. You can
fetch the metadata fields and index them into Elasticsearch with a simple
SQL select statement.
What I don't understand is why you generate an index and want to store it
in elasticsearch. You could use the plugin as Jörg suggested, transfer you
data to elasticsearch, set index:true for the fields you want and set
store:false in the mapping. This way you get an index build by
elasticsearch, can search on it, get the id as result and the data is not
stored (except metadata, if you set it to be stored). See Elasticsearch Platform — Find real-time answers at scale | Elastic
.
Using this plugin would lead to a migration from mysql data into
Elasticsearch.
So let me reformulate my question:
My infrastructure is like this:
client---->Elasticsearch
|
|
-------->mySQL
So I have a client which generates an index and some metadata for a
mail(header and body). The mail is stored in mySQL. And the client-side
generated index and metadata is stored in Elasticsearch.
The reason is because I have > 1 TB of mail content every day. This
content shall still be written to mySQL. Elasticsearch shall keep only the
index. Is that possible? And how?
I want to use Elasticsearch or only indexing and searching E-Mails. We
want to store the meta-info within Elasticsearch, keeping the content/body
of every Mail in an mySQL database. So Elasticsearch shall have a reference
to the mail body.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.