# From Coveo to Elasticsearch

**URL:** <https://discuss.elastic.co/t/from-coveo-to-elasticsearch/263457>\
**Category:** Elasticsearch\
**Created:** [February 5, 2021, 7:24pm UTC](https://discuss.elastic.co/t/from-coveo-to-elasticsearch/263457 "2021-02-05T19:24:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![manideep](https://avatars.discourse-cdn.com/v4/letter/m/6a8cbe/32.png) [@manideep](https://discuss.elastic.co/u/manideep)\
**Post date:** [February 5, 2021, 7:24pm UTC](https://discuss.elastic.co/t/from-coveo-to-elasticsearch/263457/1 "2021-02-05T19:24:35Z")

</div>

Dear Community,

I have a web application built for enterprise search using Coveo. It has lot of sources (CSVs, Excel, Sharepoint, S3, APIs, etc.) indexed using default Coveo Connectors and few custom Connector written in C#.

I wanted to build a POC for the same and be able to demonstrate the Elasticsearch Capabilities with all those sources.

**Key Points:**

1. Data is not only incremental but also mutable. Meaning, already indexed data can have changes must be able to update the changes.

2. I need a one technology to connect and index all those data sources. Be it python Client or Logstash. what is the best possibility. I do not have any logs for now.

3. One of the main reasons to move to Elasticsearch is due to open source. whereas, Coveo needs License.

BTW, I am Elastic Certified Engineer, But I don't have good experience in font-end Stack. I am looking for advise from both front-end & Back-end perspective.

I really do appreciate your recommendations/ suggestions.

Thank you!

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 5, 2021, 8:12pm UTC](https://discuss.elastic.co/t/from-coveo-to-elasticsearch/263457/2 "2021-02-05T20:12:56Z")

</div>

Welcome!

Why not using Elastic Workplace Search?

It's designed for that use case.

---

<div class="post-metadata">

**Author:** ![manideep](https://avatars.discourse-cdn.com/v4/letter/m/6a8cbe/32.png) [@manideep](https://discuss.elastic.co/u/manideep)\
**Post date:** [February 5, 2021, 9:03pm UTC](https://discuss.elastic.co/t/from-coveo-to-elasticsearch/263457/3 "2021-02-05T21:03:07Z")

</div>

Hi @dadoonet

Thank you for your response.

I'm not sure I can go with that in actual project. I can cover some extent using basic version though.

so, just wanted to go with open source stack.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 6, 2021, 5:03am UTC](https://discuss.elastic.co/t/from-coveo-to-elasticsearch/263457/4 "2021-02-06T05:03:04Z")

</div>

Up to you.

Note that Workplace Search is available in the free version with the built in basic license.

If you want to "re-implement" by yourself all the crawlers in a single tool and the UI, I'm not sure what advice I can give. As a Java developer, I'd probably go to the Java route but it's up to you.

For binary documents (PDF, etc) you can use the [ingest attachment plugin](https://www.elastic.co/guide/en/elasticsearch/plugins/current/ingest-attachment.html).

There an example here: [Using the Attachment Processor in a Pipeline | Elasticsearch Plugins and Integrations [7.10] | Elastic](https://www.elastic.co/guide/en/elasticsearch/plugins/current/using-ingest-attachment.html)

```auto
PUT _ingest/pipeline/attachment
{
  "description" : "Extract attachment information",
  "processors" : [
    {
      "attachment" : {
        "field" : "data"
      }
    }
  ]
}
PUT my_index/_doc/my_id?pipeline=attachment
{
  "data": "e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0="
}
GET my_index/_doc/my_id

```

The `data` field is basically the BASE64 representation of your binary file.

You can use [FSCrawler](https://fscrawler.readthedocs.io). There's [a tutorial](https://fscrawler.readthedocs.io/en/latest/user/tutorial.html) to help you getting started.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 6, 2021, 5:03am UTC](https://discuss.elastic.co/t/from-coveo-to-elasticsearch/263457/5 "2021-03-06T05:03:28Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.