While developing ES|QL initially, we decided to not use the Writable/NamedWritable infrastructure in Elasticsearch. This was in part due to the shared QL infrastructure code not implementing it, and not wanting to spend the dev time to do that. As we make progress on https://github.com/elastic/elasticsearch/issues/106679, those original reasons become less relevant. Migrating to the standard serialization code will reduce our surface area for maintenance and allow us to leverage the existing testing around that infrastructure.
While developing ES|QL initially, we decided to not use the
Writable
/NamedWritable
infrastructure in Elasticsearch. This was in part due to the shared QL infrastructure code not implementing it, and not wanting to spend the dev time to do that. As we make progress on https://github.com/elastic/elasticsearch/issues/106679, those original reasons become less relevant. Migrating to the standard serialization code will reduce our surface area for maintenance and allow us to leverage the existing testing around that infrastructure.