Elasticsearch's release of versions 1.3.8 and 1.4.3 has disabled the ability to send Groovy scripts dynamically by default, though Groovy remains the default scripting language. This change affects how scripts are submitted for various requests like searches and aggregations, with dynamic scripting now requiring scripts to be interpreted and compiled server-side. Despite this limitation, users can continue leveraging scripts by either using indexed scripts, which are stored and invoked by name, or by writing scripts to disk files that Elasticsearch can load and compile for future requests. While this approach may seem less dynamic, it allows scripts to be used in a controlled environment, with Groovy scripts needing to be stored in the configuration directory and loaded by Elasticsearch data nodes. To maintain flexibility and account for possible future changes in default scripting languages, it is advised to include the scripting language parameter in applications.