Urgent :adding fields mapping for nested document property

Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and these
fields need to obey certain behavior like analyzed /not analyzed or this
sort of stuff when they created.

One thing I don't know /I don't understand is how we define behavior on
keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then whether
Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/dc30baf0-7289-4aac-a45e-092fb101b296%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

In other words additional fields are stored as
{
{
Key:"field1"
Value:"value1"
}
{
Key:"field2"
Value:"value2"
}

}

field1 is created after initial field mapping, now how do I define field1
as not analyzed when it is created or do I need to change document structure

On Tuesday, 3 February 2015 23:53:29 UTC-5, bvnrwork wrote:

Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and these
fields need to obey certain behavior like analyzed /not analyzed or this
sort of stuff when they created.

One thing I don't know /I don't understand is how we define behavior on
keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then whether
Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

I think you are looking after templates.

David

Le 4 févr. 2015 à 06:51, bvnrwork budda08nitt@gmail.com a écrit :

In other words additional fields are stored as
{
{
Key:"field1"
Value:"value1"
}
{
Key:"field2"
Value:"value2"
}

}

field1 is created after initial field mapping, now how do I define field1 as not analyzed when it is created or do I need to change document structure

On Tuesday, 3 February 2015 23:53:29 UTC-5, bvnrwork wrote:
Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and these fields need to obey certain behavior like analyzed /not analyzed or this sort of stuff when they created.

One thing I don't know /I don't understand is how we define behavior on keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then whether Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
<Unknow_SizeDocs.png>

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/D3AD9049-7D8A-4CA1-9CC4-E19F8D9301B7%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

hi ,
Dynamic template is nice option which I tired but my requirement is
I want to update the key 3 mapping before indexing ..

meaning I indexed few documents with the below structure

Document
{
Key1:Value1,
Key2:Value2

}

now I want to update the mapping for key 3 in the below structure and index
some more documents ,do you have any ideas

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}
On Wednesday, 4 February 2015 01:00:55 UTC-5, David Pilato wrote:

I think you are looking after templates.

David

Le 4 févr. 2015 à 06:51, bvnrwork <budda...@gmail.com <javascript:>> a
écrit :

In other words additional fields are stored as
{
{
Key:"field1"
Value:"value1"
}
{
Key:"field2"
Value:"value2"
}

}

field1 is created after initial field mapping, now how do I define field1
as not analyzed when it is created or do I need to change document structure

On Tuesday, 3 February 2015 23:53:29 UTC-5, bvnrwork wrote:

Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and these
fields need to obey certain behavior like analyzed /not analyzed or this
sort of stuff when they created.

One thing I don't know /I don't understand is how we define behavior on
keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then whether
Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

<Unknow_SizeDocs.png>

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/6554f004-53ef-466d-9641-76df008a646b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Here is my example :

  1. Index creation request

{

"settings": {

"index": {

  "number_of_shards": 1,

  "number_of_replicas": 0

}

},

"mappings": {

"document": {

  "dynamic": "strict",

  "properties": {

    "id": {

      "type": "integer"

    },

    "rank": {

      "type": "float"

    },

    "title": {

      "type": "string"

    },

    "text": {

      "type": "string"

    },

    "path": {

      "type": "string"

    },

    "



    "fields": {

      "type": "object",

      "properties": {

        "item": {

          "type": "object",

          "properties": {}

        },

        "keys": {

          "type": "string"

        },

        "values": {

          "type": "object",

          "properties": {}

        }

      }

    }

  }

}

},

"aliases": {

"dfm032": {}

}

}

2)Index a document

{ "index" : {"_type":"document","_id":"1"} }

{"id":1,"rank":0.0,"text":"One","fields":{}}
3) Later use feels that he needs a new field with specific behavior so
trying to update the behavior

I want create this new field called "name" in fields not under document

{
"document": {
"properties": {
"name": {
"index": "analyzed",
"type": "string",
"fields": {
"name_na": {
"index": "not_analyzed",
"type": "string"
}
}
}
}
}
}

  1. After updating the mapping ,index a new document with name field

{ "index" : {"_type":"document","_id":"2"} }
{"id":2,"rank":0.0,"text":"Two","fields":{"name":"Ven Nag"}}

I don't know how to specify that new "name" field should be under fields .

Due to this 4th step fails as a enabled strict dynamic mapping

Can you help me to specify the new field "name" under fields of document ?

On Wednesday, 4 February 2015 01:00:55 UTC-5, David Pilato wrote:

I think you are looking after templates.

David

Le 4 févr. 2015 à 06:51, bvnrwork <budda...@gmail.com <javascript:>> a
écrit :

In other words additional fields are stored as
{
{
Key:"field1"
Value:"value1"
}
{
Key:"field2"
Value:"value2"
}

}

field1 is created after initial field mapping, now how do I define field1
as not analyzed when it is created or do I need to change document structure

On Tuesday, 3 February 2015 23:53:29 UTC-5, bvnrwork wrote:

Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and these
fields need to obey certain behavior like analyzed /not analyzed or this
sort of stuff when they created.

One thing I don't know /I don't understand is how we define behavior on
keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then whether
Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

<Unknow_SizeDocs.png>

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/35ba91e7-4876-400e-8102-a1fe308e3f5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hello David ,

Any quick help ? please

On Tuesday, 24 February 2015 20:32:53 UTC-5, bvnrwork wrote:

Here is my example :

  1. Index creation request

{

"settings": {

"index": {

  "number_of_shards": 1,

  "number_of_replicas": 0

}

},

"mappings": {

"document": {

  "dynamic": "strict",

  "properties": {

    "id": {

      "type": "integer"

    },

    "rank": {

      "type": "float"

    },

    "title": {

      "type": "string"

    },

    "text": {

      "type": "string"

    },

    "path": {

      "type": "string"

    },

    "



    "fields": {

      "type": "object",

      "properties": {

        "item": {

          "type": "object",

          "properties": {}

        },

        "keys": {

          "type": "string"

        },

        "values": {

          "type": "object",

          "properties": {}

        }

      }

    }

  }

}

},

"aliases": {

"dfm032": {}

}

}

2)Index a document

{ "index" : {"_type":"document","_id":"1"} }

{"id":1,"rank":0.0,"text":"One","fields":{}}
3) Later use feels that he needs a new field with specific behavior so
trying to update the behavior

I want create this new field called "name" in fields not under document

{
"document": {
"properties": {
"name": {
"index": "analyzed",
"type": "string",
"fields": {
"name_na": {
"index": "not_analyzed",
"type": "string"
}
}
}
}
}
}

  1. After updating the mapping ,index a new document with name field

{ "index" : {"_type":"document","_id":"2"} }
{"id":2,"rank":0.0,"text":"Two","fields":{"name":"Ven Nag"}}

I don't know how to specify that new "name" field should be under fields .

Due to this 4th step fails as a enabled strict dynamic mapping

Can you help me to specify the new field "name" under fields of document ?

On Wednesday, 4 February 2015 01:00:55 UTC-5, David Pilato wrote:

I think you are looking after templates.

David

Le 4 févr. 2015 à 06:51, bvnrwork budda...@gmail.com a écrit :

In other words additional fields are stored as
{
{
Key:"field1"
Value:"value1"
}
{
Key:"field2"
Value:"value2"
}

}

field1 is created after initial field mapping, now how do I define field1
as not analyzed when it is created or do I need to change document structure

On Tuesday, 3 February 2015 23:53:29 UTC-5, bvnrwork wrote:

Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and
these fields need to obey certain behavior like analyzed /not analyzed or
this sort of stuff when they created.

One thing I don't know /I don't understand is how we define behavior on
keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then whether
Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

<Unknow_SizeDocs.png>

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Any one has any ideas :slight_smile:

Regards
Nagaraju
908 517 6981

On Wed, Feb 25, 2015 at 1:16 AM, bvnrwork budda08nitt@gmail.com wrote:

Hello David ,

Any quick help ? please

On Tuesday, 24 February 2015 20:32:53 UTC-5, bvnrwork wrote:

Here is my example :

  1. Index creation request

{

"settings": {

"index": {

  "number_of_shards": 1,

  "number_of_replicas": 0

}

},

"mappings": {

"document": {

  "dynamic": "strict",

  "properties": {

    "id": {

      "type": "integer"

    },

    "rank": {

      "type": "float"

    },

    "title": {

      "type": "string"

    },

    "text": {

      "type": "string"

    },

    "path": {

      "type": "string"

    },

    "



    "fields": {

      "type": "object",

      "properties": {

        "item": {

          "type": "object",

          "properties": {}

        },

        "keys": {

          "type": "string"

        },

        "values": {

          "type": "object",

          "properties": {}

        }

      }

    }

  }

}

},

"aliases": {

"dfm032": {}

}

}

2)Index a document

{ "index" : {"_type":"document","_id":"1"} }

{"id":1,"rank":0.0,"text":"One","fields":{}}
3) Later use feels that he needs a new field with specific behavior so
trying to update the behavior

I want create this new field called "name" in fields not under document

{
"document": {
"properties": {
"name": {
"index": "analyzed",
"type": "string",
"fields": {
"name_na": {
"index": "not_analyzed",
"type": "string"
}
}
}
}
}
}

  1. After updating the mapping ,index a new document with name field

{ "index" : {"_type":"document","_id":"2"} }
{"id":2,"rank":0.0,"text":"Two","fields":{"name":"Ven Nag"}}

I don't know how to specify that new "name" field should be under fields .

Due to this 4th step fails as a enabled strict dynamic mapping

Can you help me to specify the new field "name" under fields of document
?

On Wednesday, 4 February 2015 01:00:55 UTC-5, David Pilato wrote:

I think you are looking after templates.

David

Le 4 févr. 2015 à 06:51, bvnrwork budda...@gmail.com a écrit :

In other words additional fields are stored as
{
{
Key:"field1"
Value:"value1"
}
{
Key:"field2"
Value:"value2"
}

}

field1 is created after initial field mapping, now how do I define
field1 as not analyzed when it is created or do I need to change document
structure

On Tuesday, 3 February 2015 23:53:29 UTC-5, bvnrwork wrote:

Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and
these fields need to obey certain behavior like analyzed /not analyzed or
this sort of stuff when they created.

One thing I don't know /I don't understand is how we define behavior
on keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then whether
Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

<Unknow_SizeDocs.png>

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAFtuXXL3sVbhVaHm-___jTDZe_EWBLO8KrgZnON22Qi-vP_Jhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

hi ,

Please let me know if some one has any ideas

Regards
Nagaraju
908 517 6981

On Thu, Feb 26, 2015 at 2:16 PM, buddarapu nagaraju budda08nitt@gmail.com
wrote:

Any one has any ideas :slight_smile:

Regards
Nagaraju
908 517 6981

On Wed, Feb 25, 2015 at 1:16 AM, bvnrwork budda08nitt@gmail.com wrote:

Hello David ,

Any quick help ? please

On Tuesday, 24 February 2015 20:32:53 UTC-5, bvnrwork wrote:

Here is my example :

  1. Index creation request

{

"settings": {

"index": {

  "number_of_shards": 1,

  "number_of_replicas": 0

}

},

"mappings": {

"document": {

  "dynamic": "strict",

  "properties": {

    "id": {

      "type": "integer"

    },

    "rank": {

      "type": "float"

    },

    "title": {

      "type": "string"

    },

    "text": {

      "type": "string"

    },

    "path": {

      "type": "string"

    },

    "



    "fields": {

      "type": "object",

      "properties": {

        "item": {

          "type": "object",

          "properties": {}

        },

        "keys": {

          "type": "string"

        },

        "values": {

          "type": "object",

          "properties": {}

        }

      }

    }

  }

}

},

"aliases": {

"dfm032": {}

}

}

2)Index a document

{ "index" : {"_type":"document","_id":"1"} }

{"id":1,"rank":0.0,"text":"One","fields":{}}
3) Later use feels that he needs a new field with specific behavior so
trying to update the behavior

I want create this new field called "name" in fields not under document

{
"document": {
"properties": {
"name": {
"index": "analyzed",
"type": "string",
"fields": {
"name_na": {
"index": "not_analyzed",
"type": "string"
}
}
}
}
}
}

  1. After updating the mapping ,index a new document with name field

{ "index" : {"_type":"document","_id":"2"} }
{"id":2,"rank":0.0,"text":"Two","fields":{"name":"Ven Nag"}}

I don't know how to specify that new "name" field should be under fields
.

Due to this 4th step fails as a enabled strict dynamic mapping

Can you help me to specify the new field "name" under fields of document
?

On Wednesday, 4 February 2015 01:00:55 UTC-5, David Pilato wrote:

I think you are looking after templates.

David

Le 4 févr. 2015 à 06:51, bvnrwork budda...@gmail.com a écrit :

In other words additional fields are stored as
{
{
Key:"field1"
Value:"value1"
}
{
Key:"field2"
Value:"value2"
}

}

field1 is created after initial field mapping, now how do I define
field1 as not analyzed when it is created or do I need to change document
structure

On Tuesday, 3 February 2015 23:53:29 UTC-5, bvnrwork wrote:

Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and
these fields need to obey certain behavior like analyzed /not analyzed or
this sort of stuff when they created.

One thing I don't know /I don't understand is how we define behavior
on keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then whether
Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

<Unknow_SizeDocs.png>

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAFtuXXJTpoGK%3DgBtACgNU8Xjxi3O%2BEXPwQAPCdFG2TJ1hwoTWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Could you GIST a full script?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mars 2015 à 19:05, buddarapu nagaraju budda08nitt@gmail.com a écrit :

hi ,

Please let me know if some one has any ideas

Regards
Nagaraju
908 517 6981

On Thu, Feb 26, 2015 at 2:16 PM, buddarapu nagaraju budda08nitt@gmail.com wrote:
Any one has any ideas :slight_smile:

Regards
Nagaraju
908 517 6981

On Wed, Feb 25, 2015 at 1:16 AM, bvnrwork budda08nitt@gmail.com wrote:
Hello David ,

Any quick help ? please

On Tuesday, 24 February 2015 20:32:53 UTC-5, bvnrwork wrote:
Here is my example :

  1. Index creation request

{

"settings": {

"index": {

  "number_of_shards": 1,

  "number_of_replicas": 0

}

},

"mappings": {

"document": {

  "dynamic": "strict",

  "properties": {

    "id": {

      "type": "integer"

    },

    "rank": {

      "type": "float"

    },

    "title": {

      "type": "string"

    },

    "text": {

      "type": "string"

    },

    "path": {

      "type": "string"

    },

    "



    "fields": {

      "type": "object",

      "properties": {

        "item": {

          "type": "object",

          "properties": {}

        },

        "keys": {

          "type": "string"

        },

        "values": {

          "type": "object",

          "properties": {}

        }

      }

    }

  }

}

},

"aliases": {

"dfm032": {}

}

}

2)Index a document

{ "index" : {"_type":"document","_id":"1"} }

{"id":1,"rank":0.0,"text":"One","fields":{}}

  1. Later use feels that he needs a new field with specific behavior so trying to update the behavior

I want create this new field called "name" in fields not under document

{
"document": {
"properties": {
"name": {
"index": "analyzed",
"type": "string",
"fields": {
"name_na": {
"index": "not_analyzed",
"type": "string"
}
}
}
}
}
}

  1. After updating the mapping ,index a new document with name field

{ "index" : {"_type":"document","_id":"2"} }
{"id":2,"rank":0.0,"text":"Two","fields":{"name":"Ven Nag"}}

I don't know how to specify that new "name" field should be under fields .

Due to this 4th step fails as a enabled strict dynamic mapping

Can you help me to specify the new field "name" under fields of document ?

On Wednesday, 4 February 2015 01:00:55 UTC-5, David Pilato wrote:
I think you are looking after templates.

David

Le 4 févr. 2015 à 06:51, bvnrwork budda...@gmail.com a écrit :

In other words additional fields are stored as
{
{
Key:"field1"
Value:"value1"
}
{
Key:"field2"
Value:"value2"
}

}

field1 is created after initial field mapping, now how do I define field1 as not analyzed when it is created or do I need to change document structure

On Tuesday, 3 February 2015 23:53:29 UTC-5, bvnrwork wrote:
Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and these fields need to obey certain behavior like analyzed /not analyzed or this sort of stuff when they created.

One thing I don't know /I don't understand is how we define behavior on keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then whether Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
<Unknow_SizeDocs.png>

--
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAFtuXXJTpoGK%3DgBtACgNU8Xjxi3O%2BEXPwQAPCdFG2TJ1hwoTWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/B4CDA5B9-31E3-4044-899A-688426357F0F%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Hello David ,

I want to add the field mapping after ingestion is done and have specific
document structure Document{ Id, fields{key,value}

I could able to add field mapping under document using the script but could
not under fields

so how do I specify "fields " path for field mapping when new fields added

Can you look at my script

Regards
Nagaraju
908 517 6981

On Wed, Mar 4, 2015 at 1:16 PM, David Pilato david@pilato.fr wrote:

Could you GIST a full script?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mars 2015 à 19:05, buddarapu nagaraju budda08nitt@gmail.com a
écrit :

hi ,

Please let me know if some one has any ideas

Regards
Nagaraju
908 517 6981

On Thu, Feb 26, 2015 at 2:16 PM, buddarapu nagaraju <budda08nitt@gmail.com

wrote:

Any one has any ideas :slight_smile:

Regards
Nagaraju
908 517 6981

On Wed, Feb 25, 2015 at 1:16 AM, bvnrwork budda08nitt@gmail.com wrote:

Hello David ,

Any quick help ? please

On Tuesday, 24 February 2015 20:32:53 UTC-5, bvnrwork wrote:

Here is my example :

  1. Index creation request

{

"settings": {

"index": {

  "number_of_shards": 1,

  "number_of_replicas": 0

}

},

"mappings": {

"document": {

  "dynamic": "strict",

  "properties": {

    "id": {

      "type": "integer"

    },

    "rank": {

      "type": "float"

    },

    "title": {

      "type": "string"

    },

    "text": {

      "type": "string"

    },

    "path": {

      "type": "string"

    },

    "



    "fields": {

      "type": "object",

      "properties": {

        "item": {

          "type": "object",

          "properties": {}

        },

        "keys": {

          "type": "string"

        },

        "values": {

          "type": "object",

          "properties": {}

        }

      }

    }

  }

}

},

"aliases": {

"dfm032": {}

}

}

2)Index a document

{ "index" : {"_type":"document","_id":"1"} }

{"id":1,"rank":0.0,"text":"One","fields":{}}
3) Later use feels that he needs a new field with specific behavior so
trying to update the behavior

I want create this new field called "name" in fields not under document

{
"document": {
"properties": {
"name": {
"index": "analyzed",
"type": "string",
"fields": {
"name_na": {
"index": "not_analyzed",
"type": "string"
}
}
}
}
}
}

  1. After updating the mapping ,index a new document with name field

{ "index" : {"_type":"document","_id":"2"} }
{"id":2,"rank":0.0,"text":"Two","fields":{"name":"Ven Nag"}}

I don't know how to specify that new "name" field should be under
fields .

Due to this 4th step fails as a enabled strict dynamic mapping

Can you help me to specify the new field "name" under fields of
document ?

On Wednesday, 4 February 2015 01:00:55 UTC-5, David Pilato wrote:

I think you are looking after templates.

David

Le 4 févr. 2015 à 06:51, bvnrwork budda...@gmail.com a écrit :

In other words additional fields are stored as
{
{
Key:"field1"
Value:"value1"
}
{
Key:"field2"
Value:"value2"
}

}

field1 is created after initial field mapping, now how do I define
field1 as not analyzed when it is created or do I need to change document
structure

On Tuesday, 3 February 2015 23:53:29 UTC-5, bvnrwork wrote:

Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and
these fields need to obey certain behavior like analyzed /not analyzed or
this sort of stuff when they created.

One thing I don't know /I don't understand is how we define behavior
on keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then
whether Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

<Unknow_SizeDocs.png>

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAFtuXXJTpoGK%3DgBtACgNU8Xjxi3O%2BEXPwQAPCdFG2TJ1hwoTWg%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAFtuXXJTpoGK%3DgBtACgNU8Xjxi3O%2BEXPwQAPCdFG2TJ1hwoTWg%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/B4CDA5B9-31E3-4044-899A-688426357F0F%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/B4CDA5B9-31E3-4044-899A-688426357F0F%40pilato.fr?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAFtuXXLc4m75ktzyKrkr794Y4ka_nK0rGX7UovNUzKOUQ219Jw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Where is your script?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mars 2015 à 19:22, buddarapu nagaraju budda08nitt@gmail.com a écrit :

Hello David ,

I want to add the field mapping after ingestion is done and have specific document structure Document{ Id, fields{key,value}

I could able to add field mapping under document using the script but could not under fields

so how do I specify "fields " path for field mapping when new fields added

Can you look at my script

Regards
Nagaraju
908 517 6981

On Wed, Mar 4, 2015 at 1:16 PM, David Pilato david@pilato.fr wrote:
Could you GIST a full script?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mars 2015 à 19:05, buddarapu nagaraju budda08nitt@gmail.com a écrit :

hi ,

Please let me know if some one has any ideas

Regards
Nagaraju
908 517 6981

On Thu, Feb 26, 2015 at 2:16 PM, buddarapu nagaraju budda08nitt@gmail.com wrote:
Any one has any ideas :slight_smile:

Regards
Nagaraju
908 517 6981

On Wed, Feb 25, 2015 at 1:16 AM, bvnrwork budda08nitt@gmail.com wrote:
Hello David ,

Any quick help ? please

On Tuesday, 24 February 2015 20:32:53 UTC-5, bvnrwork wrote:
Here is my example :

  1. Index creation request

{

"settings": {

"index": {

  "number_of_shards": 1,

  "number_of_replicas": 0

}

},

"mappings": {

"document": {

  "dynamic": "strict",

  "properties": {

    "id": {

      "type": "integer"

    },

    "rank": {

      "type": "float"

    },

    "title": {

      "type": "string"

    },

    "text": {

      "type": "string"

    },

    "path": {

      "type": "string"

    },

    "



    "fields": {

      "type": "object",

      "properties": {

        "item": {

          "type": "object",

          "properties": {}

        },

        "keys": {

          "type": "string"

        },

        "values": {

          "type": "object",

          "properties": {}

        }

      }

    }

  }

}

},

"aliases": {

"dfm032": {}

}

}

2)Index a document

{ "index" : {"_type":"document","_id":"1"} }

{"id":1,"rank":0.0,"text":"One","fields":{}}

  1. Later use feels that he needs a new field with specific behavior so trying to update the behavior

I want create this new field called "name" in fields not under document

{
"document": {
"properties": {
"name": {
"index": "analyzed",
"type": "string",
"fields": {
"name_na": {
"index": "not_analyzed",
"type": "string"
}
}
}
}
}
}

  1. After updating the mapping ,index a new document with name field

{ "index" : {"_type":"document","_id":"2"} }
{"id":2,"rank":0.0,"text":"Two","fields":{"name":"Ven Nag"}}

I don't know how to specify that new "name" field should be under fields .

Due to this 4th step fails as a enabled strict dynamic mapping

Can you help me to specify the new field "name" under fields of document ?

On Wednesday, 4 February 2015 01:00:55 UTC-5, David Pilato wrote:
I think you are looking after templates.

David

Le 4 févr. 2015 à 06:51, bvnrwork budda...@gmail.com a écrit :

In other words additional fields are stored as
{
{
Key:"field1"
Value:"value1"
}
{
Key:"field2"
Value:"value2"
}

}

field1 is created after initial field mapping, now how do I define field1 as not analyzed when it is created or do I need to change document structure

On Tuesday, 3 February 2015 23:53:29 UTC-5, bvnrwork wrote:
Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and these fields need to obey certain behavior like analyzed /not analyzed or this sort of stuff when they created.

One thing I don't know /I don't understand is how we define behavior on keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then whether Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
<Unknow_SizeDocs.png>

--
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAFtuXXJTpoGK%3DgBtACgNU8Xjxi3O%2BEXPwQAPCdFG2TJ1hwoTWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/B4CDA5B9-31E3-4044-899A-688426357F0F%40pilato.fr.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAFtuXXLc4m75ktzyKrkr794Y4ka_nK0rGX7UovNUzKOUQ219Jw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1CDA334A-7DFD-49B9-A02F-60E8DA0D0A2B%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Here is my example :

  1. Index creation request

{

"settings": {

"index": {

  "number_of_shards": 1,

  "number_of_replicas": 0

}

},

"mappings": {

"document": {

  "dynamic": "strict",

  "properties": {

    "id": {

      "type": "integer"

    },

    "rank": {

      "type": "float"

    },

    "title": {

      "type": "string"

    },

    "text": {

      "type": "string"

    },

    "path": {

      "type": "string"

    },

    "



    "fields": {

      "type": "object",

      "properties": {

        "item": {

          "type": "object",

          "properties": {}

        },

        "keys": {

          "type": "string"

        },

        "values": {

          "type": "object",

          "properties": {}

        }

      }

    }

  }

}

},

"aliases": {

"dfm032": {}

}

}

2)Index a document

{ "index" : {"_type":"document","_id":"1"} }

{"id":1,"rank":0.0,"text":"One","fields":{}}
3) Later use feels that he needs a new field with specific behavior so
trying to update the behavior

I want create this new field called "name" in fields not under document

{
"document": {
"properties": {
"name": {
"index": "analyzed",
"type": "string",
"fields": {
"name_na": {
"index": "not_analyzed",
"type": "string"
}
}
}
}
}
}

  1. After updating the mapping ,index a new document with name field

{ "index" : {"_type":"document","_id":"2"} }
{"id":2,"rank":0.0,"text":"Two","fields":{"name":"Ven Nag"}}

I don't know how to specify that new "name" field should be under fields .

Due to this 4th step fails as a enabled strict dynamic mapping

Can you help me to specify the new field "name" under fields of document ?

Regards
Nagaraju
908 517 6981

On Wed, Mar 4, 2015 at 1:29 PM, David Pilato david@pilato.fr wrote:

Where is your script?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mars 2015 à 19:22, buddarapu nagaraju budda08nitt@gmail.com a
écrit :

Hello David ,

I want to add the field mapping after ingestion is done and have specific
document structure Document{ Id, fields{key,value}

I could able to add field mapping under document using the script but
could not under fields

so how do I specify "fields " path for field mapping when new fields added

Can you look at my script

Regards
Nagaraju
908 517 6981

On Wed, Mar 4, 2015 at 1:16 PM, David Pilato david@pilato.fr wrote:

Could you GIST a full script?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mars 2015 à 19:05, buddarapu nagaraju budda08nitt@gmail.com a
écrit :

hi ,

Please let me know if some one has any ideas

Regards
Nagaraju
908 517 6981

On Thu, Feb 26, 2015 at 2:16 PM, buddarapu nagaraju <
budda08nitt@gmail.com> wrote:

Any one has any ideas :slight_smile:

Regards
Nagaraju
908 517 6981

On Wed, Feb 25, 2015 at 1:16 AM, bvnrwork budda08nitt@gmail.com wrote:

Hello David ,

Any quick help ? please

On Tuesday, 24 February 2015 20:32:53 UTC-5, bvnrwork wrote:

Here is my example :

  1. Index creation request

{

"settings": {

"index": {

  "number_of_shards": 1,

  "number_of_replicas": 0

}

},

"mappings": {

"document": {

  "dynamic": "strict",

  "properties": {

    "id": {

      "type": "integer"

    },

    "rank": {

      "type": "float"

    },

    "title": {

      "type": "string"

    },

    "text": {

      "type": "string"

    },

    "path": {

      "type": "string"

    },

    "



    "fields": {

      "type": "object",

      "properties": {

        "item": {

          "type": "object",

          "properties": {}

        },

        "keys": {

          "type": "string"

        },

        "values": {

          "type": "object",

          "properties": {}

        }

      }

    }

  }

}

},

"aliases": {

"dfm032": {}

}

}

2)Index a document

{ "index" : {"_type":"document","_id":"1"} }

{"id":1,"rank":0.0,"text":"One","fields":{}}
3) Later use feels that he needs a new field with specific behavior so
trying to update the behavior

I want create this new field called "name" in fields not under document

{
"document": {
"properties": {
"name": {
"index": "analyzed",
"type": "string",
"fields": {
"name_na": {
"index": "not_analyzed",
"type": "string"
}
}
}
}
}
}

  1. After updating the mapping ,index a new document with name field

{ "index" : {"_type":"document","_id":"2"} }
{"id":2,"rank":0.0,"text":"Two","fields":{"name":"Ven Nag"}}

I don't know how to specify that new "name" field should be under
fields .

Due to this 4th step fails as a enabled strict dynamic mapping

Can you help me to specify the new field "name" under fields of
document ?

On Wednesday, 4 February 2015 01:00:55 UTC-5, David Pilato wrote:

I think you are looking after templates.

David

Le 4 févr. 2015 à 06:51, bvnrwork budda...@gmail.com a écrit :

In other words additional fields are stored as
{
{
Key:"field1"
Value:"value1"
}
{
Key:"field2"
Value:"value2"
}

}

field1 is created after initial field mapping, now how do I define
field1 as not analyzed when it is created or do I need to change document
structure

On Tuesday, 3 February 2015 23:53:29 UTC-5, bvnrwork wrote:

Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and
these fields need to obey certain behavior like analyzed /not analyzed or
this sort of stuff when they created.

One thing I don't know /I don't understand is how we define
behavior on keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then
whether Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

<Unknow_SizeDocs.png>

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAFtuXXJTpoGK%3DgBtACgNU8Xjxi3O%2BEXPwQAPCdFG2TJ1hwoTWg%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAFtuXXJTpoGK%3DgBtACgNU8Xjxi3O%2BEXPwQAPCdFG2TJ1hwoTWg%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/B4CDA5B9-31E3-4044-899A-688426357F0F%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/B4CDA5B9-31E3-4044-899A-688426357F0F%40pilato.fr?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAFtuXXLc4m75ktzyKrkr794Y4ka_nK0rGX7UovNUzKOUQ219Jw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAFtuXXLc4m75ktzyKrkr794Y4ka_nK0rGX7UovNUzKOUQ219Jw%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/1CDA334A-7DFD-49B9-A02F-60E8DA0D0A2B%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/1CDA334A-7DFD-49B9-A02F-60E8DA0D0A2B%40pilato.fr?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAFtuXXJYRFyxkb1jL8qUg5Kj%3Dx%3DeuML3s4pofTRG2Wj5pU29zw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

How can we execute it?
Please look at http://www.elasticsearch.org/help/ http://www.elasticsearch.org/help/
For example, this is a CURL recreation: https://gist.github.com/dadoonet/2965777#file-test-sh https://gist.github.com/dadoonet/2965777#file-test-sh

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr https://twitter.com/elasticsearchfr | @scrutmydocs https://twitter.com/scrutmydocs

Le 4 mars 2015 à 21:04, buddarapu nagaraju budda08nitt@gmail.com a écrit :

Here is my example :

  1. Index creation request

{

"settings": {

"index": {

  "number_of_shards": 1,

  "number_of_replicas": 0

}

},

"mappings": {

"document": {

  "dynamic": "strict",

  "properties": {

    "id": {

      "type": "integer"

    },

    "rank": {

      "type": "float"

    },

    "title": {

      "type": "string"

    },

    "text": {

      "type": "string"

    },

    "path": {

      "type": "string"

    },

    "



    "fields": {

      "type": "object",

      "properties": {

        "item": {

          "type": "object",

          "properties": {}

        },

        "keys": {

          "type": "string"

        },

        "values": {

          "type": "object",

          "properties": {}

        }

      }

    }

  }

}

},

"aliases": {

"dfm032": {}

}

}

2)Index a document

{ "index" : {"_type":"document","_id":"1"} }

{"id":1,"rank":0.0,"text":"One","fields":{}}

  1. Later use feels that he needs a new field with specific behavior so trying to update the behavior

I want create this new field called "name" in fields not under document

{
"document": {
"properties": {
"name": {
"index": "analyzed",
"type": "string",
"fields": {
"name_na": {
"index": "not_analyzed",
"type": "string"
}
}
}
}
}
}

  1. After updating the mapping ,index a new document with name field

{ "index" : {"_type":"document","_id":"2"} }
{"id":2,"rank":0.0,"text":"Two","fields":{"name":"Ven Nag"}}

I don't know how to specify that new "name" field should be under fields .

Due to this 4th step fails as a enabled strict dynamic mapping

Can you help me to specify the new field "name" under fields of document ?

Regards
Nagaraju
908 517 6981

On Wed, Mar 4, 2015 at 1:29 PM, David Pilato <david@pilato.fr mailto:david@pilato.fr> wrote:
Where is your script?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mars 2015 à 19:22, buddarapu nagaraju <budda08nitt@gmail.com mailto:budda08nitt@gmail.com> a écrit :

Hello David ,

I want to add the field mapping after ingestion is done and have specific document structure Document{ Id, fields{key,value}

I could able to add field mapping under document using the script but could not under fields

so how do I specify "fields " path for field mapping when new fields added

Can you look at my script

Regards
Nagaraju
908 517 6981 tel:908%20517%206981
On Wed, Mar 4, 2015 at 1:16 PM, David Pilato <david@pilato.fr mailto:david@pilato.fr> wrote:
Could you GIST a full script?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mars 2015 à 19:05, buddarapu nagaraju <budda08nitt@gmail.com mailto:budda08nitt@gmail.com> a écrit :

hi ,

Please let me know if some one has any ideas

Regards
Nagaraju
908 517 6981 tel:908%20517%206981
On Thu, Feb 26, 2015 at 2:16 PM, buddarapu nagaraju <budda08nitt@gmail.com mailto:budda08nitt@gmail.com> wrote:
Any one has any ideas :slight_smile:

Regards
Nagaraju
908 517 6981 tel:908%20517%206981

On Wed, Feb 25, 2015 at 1:16 AM, bvnrwork <budda08nitt@gmail.com mailto:budda08nitt@gmail.com> wrote:
Hello David ,

Any quick help ? please

On Tuesday, 24 February 2015 20:32:53 UTC-5, bvnrwork wrote:
Here is my example :

  1. Index creation request

{

"settings": {

"index": {

  "number_of_shards": 1,

  "number_of_replicas": 0

}

},

"mappings": {

"document": {

  "dynamic": "strict",

  "properties": {

    "id": {

      "type": "integer"

    },

    "rank": {

      "type": "float"

    },

    "title": {

      "type": "string"

    },

    "text": {

      "type": "string"

    },

    "path": {

      "type": "string"

    },

    "


    "fields": {

      "type": "object",

      "properties": {

        "item": {

          "type": "object",

          "properties": {}

        },

        "keys": {

          "type": "string"

        },

        "values": {

          "type": "object",

          "properties": {}

        }

      }

    }

  }

}

},

"aliases": {

"dfm032": {}

}

}

2)Index a document

{ "index" : {"_type":"document","_id":"1"} }

{"id":1,"rank":0.0,"text":"One","fields":{}}

  1. Later use feels that he needs a new field with specific behavior so trying to update the behavior

I want create this new field called "name" in fields not under document

{
"document": {
"properties": {
"name": {
"index": "analyzed",
"type": "string",
"fields": {
"name_na": {
"index": "not_analyzed",
"type": "string"
}
}
}
}
}
}

  1. After updating the mapping ,index a new document with name field

{ "index" : {"_type":"document","_id":"2"} }
{"id":2,"rank":0.0,"text":"Two","fields":{"name":"Ven Nag"}}

I don't know how to specify that new "name" field should be under fields .

Due to this 4th step fails as a enabled strict dynamic mapping

Can you help me to specify the new field "name" under fields of document ?

On Wednesday, 4 February 2015 01:00:55 UTC-5, David Pilato wrote:
I think you are looking after templates.

David

Le 4 févr. 2015 à 06:51, bvnrwork <budda...@gmail.com <>> a écrit :

In other words additional fields are stored as
{
{
Key:"field1"
Value:"value1"
}
{
Key:"field2"
Value:"value2"
}

}

field1 is created after initial field mapping, now how do I define field1 as not analyzed when it is created or do I need to change document structure

On Tuesday, 3 February 2015 23:53:29 UTC-5, bvnrwork wrote:
Hi,

We have Document structure like this

Document
{
Key1:Value1
Key2:Value2
Key3:Value3,
Key4:Valu4
List<key,Value> AdditionalFields;
}

Additional fields are the dynamic fields(they can grow or sink) and these fields need to obey certain behavior like analyzed /not analyzed or this sort of stuff when they created.

One thing I don't know /I don't understand is how we define behavior on keys (Fields /field names) from Additional fields ?

For below example document :

Document
{
Key1:Value1,
Key2:Value2
AdditionalFields
{
Key3:Value3
}

If I define Key3 as not analyzed in the index definition then whether Value3 is not going to analyzed

Or Is there a way to do this ?

Regards,
Nagaraju

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@googlegroups.com <>.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/3921832e-47e5-4565-abed-d57b6aea2aaf%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.
<Unknow_SizeDocs.png>

--
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/eef4eaae-32dc-4e67-b0dd-8cd964376aca%40googlegroups.com?utm_medium=email&utm_source=footer.

For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAFtuXXJTpoGK%3DgBtACgNU8Xjxi3O%2BEXPwQAPCdFG2TJ1hwoTWg%40mail.gmail.com https://groups.google.com/d/msgid/elasticsearch/CAFtuXXJTpoGK%3DgBtACgNU8Xjxi3O%2BEXPwQAPCdFG2TJ1hwoTWg%40mail.gmail.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/B4CDA5B9-31E3-4044-899A-688426357F0F%40pilato.fr https://groups.google.com/d/msgid/elasticsearch/B4CDA5B9-31E3-4044-899A-688426357F0F%40pilato.fr?utm_medium=email&utm_source=footer.

For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAFtuXXLc4m75ktzyKrkr794Y4ka_nK0rGX7UovNUzKOUQ219Jw%40mail.gmail.com https://groups.google.com/d/msgid/elasticsearch/CAFtuXXLc4m75ktzyKrkr794Y4ka_nK0rGX7UovNUzKOUQ219Jw%40mail.gmail.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe https://groups.google.com/d/topic/elasticsearch/t9jgOkWUe60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1CDA334A-7DFD-49B9-A02F-60E8DA0D0A2B%40pilato.fr https://groups.google.com/d/msgid/elasticsearch/1CDA334A-7DFD-49B9-A02F-60E8DA0D0A2B%40pilato.fr?utm_medium=email&utm_source=footer.

For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAFtuXXJYRFyxkb1jL8qUg5Kj%3Dx%3DeuML3s4pofTRG2Wj5pU29zw%40mail.gmail.com https://groups.google.com/d/msgid/elasticsearch/CAFtuXXJYRFyxkb1jL8qUg5Kj%3Dx%3DeuML3s4pofTRG2Wj5pU29zw%40mail.gmail.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/005B8C4E-CDBB-49F7-80FD-960A08908A0E%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.