# Translate Dictionary Path Updating of Changes **URL:** \ **Category:** Logstash\ **Created:** [April 13, 2016, 7:41pm UTC](https://discuss.elastic.co/t/translate-dictionary-path-updating-of-changes/47303 "2016-04-13T19:41:55Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![neu5ron](https://avatars.discourse-cdn.com/v4/letter/n/0ea827/32.png) [@neu5ron](https://discuss.elastic.co/u/neu5ron)\ **Post date:** [April 13, 2016, 7:41pm UTC](https://discuss.elastic.co/t/translate-dictionary-path-updating-of-changes/47303/1 "2016-04-13T19:41:55Z")
In the article for [https://www.elastic.co/blog/bro-ids-elastic-stack](https://www.elastic.co/blog/bro-ids-elastic-stack) (great article by the way) may want to note to users that if they are continuously updating a file, that the dictionary\_path in translate points at, that they should either add periodic\_flush =\> "true" or restart logstash after file is updated. Is that the correct way to go about making sure changes to a dictionary\_path are implemented or is there a more efficient way? ---
**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:** [April 14, 2016, 1:03am UTC](https://discuss.elastic.co/t/translate-dictionary-path-updating-of-changes/47303/2 "2016-04-14T01:03:18Z")
LS 2.3 has dynamic config reloading, so you can leverage that as well. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 5:02am UTC](https://discuss.elastic.co/t/translate-dictionary-path-updating-of-changes/47303/3 "2017-07-06T05:02:23Z")