# Creating index ~ mapping rdbms to index

**URL:** <https://discuss.elastic.co/t/creating-index-mapping-rdbms-to-index/230082>\
**Category:** Elasticsearch\
**Created:** [April 28, 2020, 6:02am UTC](https://discuss.elastic.co/t/creating-index-mapping-rdbms-to-index/230082 "2020-04-28T06:02:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rajiv\_d](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rajiv_d/32/66399_2.png) [@rajiv\_d](https://discuss.elastic.co/u/rajiv_d)\
**Post date:** [April 28, 2020, 6:02am UTC](https://discuss.elastic.co/t/creating-index-mapping-rdbms-to-index/230082/1 "2020-04-28T06:02:26Z")

</div>

We have an existing sql data from where we kind of planning to get only aggregated entity which is bounded by key constraints which is mapped to index .

Now my query , is it good to have one sql table or entity per index or table with constraints being aggregated as index .

but going with aggregated data would have complex mapping built but it does reduce the number of indexes being created in future .

And creating single entity per index , would mean relative search with one key found being targeted from other index to get aggregate result which may not be the right way to go according to me .

Kindly let me know on this which would be the better approach .

---

<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:** [May 26, 2020, 6:13am UTC](https://discuss.elastic.co/t/creating-index-mapping-rdbms-to-index/230082/2 "2020-05-26T06:13:21Z")

</div>

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