# \_timestamp deprecated **URL:** \ **Category:** Elasticsearch\ **Created:** [January 6, 2016, 2:54pm UTC](https://discuss.elastic.co/t/-timestamp-deprecated/38514 "2016-01-06T14:54:42Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![israel](https://avatars.discourse-cdn.com/v4/letter/i/b77776/32.png) [@israel](https://discuss.elastic.co/u/israel)\ **Post date:** [January 6, 2016, 2:54pm UTC](https://discuss.elastic.co/t/-timestamp-deprecated/38514/1 "2016-01-06T14:54:42Z")
Hi, Is \_timestamp meta field is deprecated or just the path on \_timestamp? If it is completely deprecated, why? Thanks, Israel ---
**Author:** ![bleskes](https://avatars.discourse-cdn.com/v4/letter/b/71c47a/32.png) [@bleskes](https://discuss.elastic.co/u/bleskes)\ **Post date:** [January 6, 2016, 7:49pm UTC](https://discuss.elastic.co/t/-timestamp-deprecated/38514/2 "2016-01-06T19:49:33Z")
Hi. Both are deprecated but they will keep on working for the 2.x series (see [https://www.elastic.co/guide/en/elasticsearch/reference/2.1/breaking\_20\_mapping\_changes.html#\_literal\_\_timestamp\_literal\_and\_literal\_\_ttl\_literal\_deprecated](https://www.elastic.co/guide/en/elasticsearch/reference/2.1/breaking_20_mapping_changes.html#_literal __timestamp_literal_and_literal__ ttl_literal_deprecated) ) . The main reason is that we feel it will be simpler if the ttl logic will work on any field (not only a pre determined fixed `_timestamp` ). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 6, 2016, 7:54pm UTC](https://discuss.elastic.co/t/-timestamp-deprecated/38514/3 "2016-01-06T19:54:09Z")
See also [https://github.com/elastic/elasticsearch/issues/15644](https://github.com/elastic/elasticsearch/issues/15644) ---
**Author:** ![israel](https://avatars.discourse-cdn.com/v4/letter/i/b77776/32.png) [@israel](https://discuss.elastic.co/u/israel)\ **Post date:** [January 7, 2016, 7:09am UTC](https://discuss.elastic.co/t/-timestamp-deprecated/38514/4 "2016-01-07T07:09:04Z")
@bleskes So why remove \_timestamp? just change ttl to work on other user fields as well.. @warkolm I agree with @lam-juice and can add another scenario where system \_timestamp field is better then a user date field: A retry scenario, in a case some documents failed to index due to load issues, the user defines "timestamp" field will have to be recalculated and inserted into the index request source.... ---
**Author:** ![bleskes](https://avatars.discourse-cdn.com/v4/letter/b/71c47a/32.png) [@bleskes](https://discuss.elastic.co/u/bleskes)\ **Post date:** [January 7, 2016, 7:57am UTC](https://discuss.elastic.co/t/-timestamp-deprecated/38514/5 "2016-01-07T07:57:22Z")
@israel current thinking is to allow you set any date field via the coming Ingest feature, ( [https://github.com/elastic/elasticsearch/issues/14049](https://github.com/elastic/elasticsearch/issues/14049) ). ---
**Author:** ![israel](https://avatars.discourse-cdn.com/v4/letter/i/b77776/32.png) [@israel](https://discuss.elastic.co/u/israel)\ **Post date:** [January 7, 2016, 8:25am UTC](https://discuss.elastic.co/t/-timestamp-deprecated/38514/6 "2016-01-07T08:25:26Z")
Sounds very interesting and useful. However, I would not disable a basic system field as timestamp. Parsing and modifying json sources every time, just to have the real timestamp functionality has a performance cost. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:26pm UTC](https://discuss.elastic.co/t/-timestamp-deprecated/38514/7 "2017-07-05T23:26:30Z")