# Any chances that CrateDB will support \_all fields like ES does right now?

**URL:** <https://community.cratedb.com/t/any-chances-that-cratedb-will-support-all-fields-like-es-does-right-now/145>\
**Category:** CrateDB\
**Created:** [February 11, 2019, 2:32pm UTC](https://community.cratedb.com/t/any-chances-that-cratedb-will-support-all-fields-like-es-does-right-now/145 "2019-02-11T14:32:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![chughpiyush](https://avatars.discourse-cdn.com/v4/letter/c/7ea924/32.png) [@chughpiyush](https://community.cratedb.com/u/chughpiyush)\
**Post date:** [February 11, 2019, 2:32pm UTC](https://community.cratedb.com/t/any-chances-that-cratedb-will-support-all-fields-like-es-does-right-now/145/1 "2019-02-11T14:32:31Z")

</div>

In ES:

> The `copy_to` parameter allows you to create custom [`_all`](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-all-field.html) fields. In other words, the values of multiple fields can be copied into a group field, which can then be queried as a single field.

Right now CrateDB does not support having such a dynamic column based on a combination of other columns. Do we have such a feature in pipeline?

[https://www.elastic.co/guide/en/elasticsearch/reference/current/copy-to.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/copy-to.html)

---

<div class="post-metadata">

**Author:** ![mfussenegger](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/mfussenegger/32/79_2.png) [@mfussenegger](https://community.cratedb.com/u/mfussenegger)\
**Post date:** [February 12, 2019, 9:58pm UTC](https://community.cratedb.com/t/any-chances-that-cratedb-will-support-all-fields-like-es-does-right-now/145/2 "2019-02-12T21:58:16Z")

</div>

Given that `_all` is deprecated in ES it is very unlikely that we’ll add support for it.

CrateDB exposes something similar to `copy-to` with [composite indices](https://crate.io/docs/crate/reference/en/latest/general/ddl/fulltext-indices.html#defining-a-composite-index).

---

<div class="post-metadata">

**Author:** ![chughpiyush](https://avatars.discourse-cdn.com/v4/letter/c/7ea924/32.png) [@chughpiyush](https://community.cratedb.com/u/chughpiyush)\
**Post date:** [February 13, 2019, 10:39am UTC](https://community.cratedb.com/t/any-chances-that-cratedb-will-support-all-fields-like-es-does-right-now/145/3 "2019-02-13T10:39:00Z")

</div>

Thanks @mfussenegger 🙂

---

<div class="post-metadata">

**Author:** ![sambhav](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/sambhav/32/293_2.png) [@sambhav](https://community.cratedb.com/u/sambhav)\
**Post date:** [May 15, 2019, 9:04am UTC](https://community.cratedb.com/t/any-chances-that-cratedb-will-support-all-fields-like-es-does-right-now/145/4 "2019-05-15T09:04:48Z")

</div>

This is our table initially;

```
create table documents_a (
... title text,
... body text,
... INDEX title_body_ft
... using fulltext(title, body) with (analyzer = 'english')
... )

```

**Now suppose we need to add a column (new\_column) in ‘documents\_a’ for that we need to create our table again and re-index data.**

```
create table documents_a (
... title text,
... body text,
... new_column text,
... INDEX title_body_ft
... using fulltext(title, body,new_column) with (analyzer = 'english')
... )

```

**Now my questions are:**

1. Any alternative solution for adding ‘new\_column’ in ‘title\_body\_ft’ without creating the table again?
2. How to avoid re-indexing here?

@mfussenegger any help would be much appreciated?