# \[Canvas\] Mapping Conflict in Index Alias leads to failing visualizations

**URL:** <https://discuss.elastic.co/t/canvas-mapping-conflict-in-index-alias-leads-to-failing-visualizations/158143>\
**Category:** Kibana\
**Tags:** canvas\
**Created:** [November 26, 2018, 9:28am UTC](https://discuss.elastic.co/t/canvas-mapping-conflict-in-index-alias-leads-to-failing-visualizations/158143 "2018-11-26T09:28:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tarkin67](https://avatars.discourse-cdn.com/v4/letter/t/8797f3/32.png) [@tarkin67](https://discuss.elastic.co/u/tarkin67)\
**Post date:** [November 26, 2018, 9:28am UTC](https://discuss.elastic.co/t/canvas-mapping-conflict-in-index-alias-leads-to-failing-visualizations/158143/1 "2018-11-26T09:28:35Z")

</div>

Hi all,

I used the canvas plugin to create a workpad with Kibana 6.4.2. After the upgrade to 6.5.x with canvas built in, all visualizations that query a certain index alias fail. The alias points to two indices, one having a "message" field mapped to _text_ and the other having a "message" field mapped to _object_.

In the previous version the visualizations were displayed but as of 6.5.0, canvas refuses to do anything with this: ![grafik](https://us1.discourse-cdn.com/elastic/original/3X/c/c/cccf96ed148c9dd2d09e6156c4dafeece6e2e6d4.png)

Also, when querying for a field that does currently not exist in the index, canvas shows an error message and refuses to show the visualization. Wouldn't it make more sense to just display the visualization without the data from that field? I think this was also the way that it was handled in the previous canvas version but I might be wrong here.

Do you guys have any suggestions on how I can work around these issues?

Thanks in advance and kind regards,  
Kasimir

---

<div class="post-metadata">

**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\
**Post date:** [November 26, 2018, 9:18pm UTC](https://discuss.elastic.co/t/canvas-mapping-conflict-in-index-alias-leads-to-failing-visualizations/158143/2 "2018-11-26T21:18:17Z")

</div>

Hi @tarkin67, please create an issue on our [Github repo](https://github.com/elastic/kibana). From what you've said it sounds like there may have been an inadvertent breaking change. Keep in mind Canvas is still in beta though, so breakages may occur.

---

<div class="post-metadata">

**Author:** ![tarkin67](https://avatars.discourse-cdn.com/v4/letter/t/8797f3/32.png) [@tarkin67](https://discuss.elastic.co/u/tarkin67)\
**Post date:** [November 27, 2018, 9:21am UTC](https://discuss.elastic.co/t/canvas-mapping-conflict-in-index-alias-leads-to-failing-visualizations/158143/3 "2018-11-27T09:21:02Z")

</div>

Thank you for your reply @Bargs! I opened [this](https://github.com/elastic/kibana/issues/26240) issue on github.

---

<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:** [December 25, 2018, 9:21am UTC](https://discuss.elastic.co/t/canvas-mapping-conflict-in-index-alias-leads-to-failing-visualizations/158143/4 "2018-12-25T09:21:09Z")

</div>

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