You could do it if you have a very primitive data structure - but it is a task where you will get very dirty hands. Because the structure of the JSON in Elastic Search is optimized for search while the JSON in IWA_BusinessData is optimized for beeing perfectly serializable by Java. Main differences: - elastic search JSON knows no java types. If you have an abstract type in your data, the concrete type that was serialized must be written into the JSON or the JVM does not know which type to instantiate while deserialization - elastic search JSON does not knows objects that are equally used multiple times within the same object tree. Means if you used for instance an instance of Person that is refered multiple times in the same root Business Data you have no way to load this data with the JVM and know that the objects are the same. - elastic search JSON stores arrays in different format. Deserializtion will fail in the JVM so So no. You In case of a data loss, one should better restore the data from a backup dump of your the database. But you can try to re-store the JSON structure that IWA_BusinessData likes if you have a very simple object hierarchy - because then the JSON may could be easily refactored by hand.

You could do it if you have a very primitive data structure - but it is a task where you will get very dirty hands. Because the structure of the JSON in Elastic Search is optimized for search while the JSON in IWA_BusinessData is optimized for beeing perfectly serializable by a Java. Main differences: - elastic search JSON knows no java types. If you have an abstract type in your data, the concrete type that was serialized must be written into the JSON or the JVM does not know which type to instantiate while deserialization - elastic search JSON does not knows objects that are equally used multiple times within the same object tree. Means if you used for instance an instance of Person that is refered multiple times in the same root Business Data you have no way to load this data with the JVM and know that the objects are the same. - elastic search JSON stores arrays in different format. Deserializtion will fail in the JVM so no. You should better restore the data from a backup dump of your database. But you can try to re-store the JSON structure that IWA_BusinessData likes if you have a very simple object hierarchy - because then the JSON may could be easily refactored by hand.

You could do it if you have a very primitive data structure - but it is a task where you will get very dirty hands. Because the structure of the JSON in Elastic Search is optimized for search while the JSON in IWA_BusinessData is optimized for beeing perfectly serializable by a Java. Main differences: - elastic search JSON knows no java types. If you have an abstract type in your data, the concrete type that was serialized must be written into the JSON or the JVM does not know which type to instantiate while deserialization - elastic search JSON does not knows objects that are equally used multiple times within the same object tree. Means if you used for instance an instance of Person that is refered multiple times in the same root Business Data you have no way to load this data with the JVM and know that the objects are the same. - elastic search JSON stores arrays in different format. Deserializtion will fail in the JVM so no. You should better restore the data from a backup dump of your database. And otherwise you will have But you can try to compare the two JSON formats re-store the JSON structure that IWA_BusinessData likes if you have a very simple object hierarchy - because then the JSON may could be easily refactored by hand and apply migrations....hand.

You could do it if you have a very primitive data structure - but it will be a default a task where you will get very dirty hands. Because the structure of the JSON in Elastic Search is optimized for search while the JSON in IWA_BusinessData is optimized for beeing perfectly serializable by a Java. Main differences: - elastic search JSON knows no java types. If you have an abstract type in your data, the concrete type that was serialized must be written into the JSON or the JVM does not know which type to instantiate while deserialization - elastic search JSON does not knows objects that are equally used multiple times within the same object tree. Means if you used for instance an instance of Person that is refered multiple times in the same root Business Data you have no way to load this data with the JVM and know that the objects are the same. - elastic search JSON stores arrays in different format. Deserializtion will fail in the JVM so no. You should better restore the data from a backup dump of your database.database. And otherwise you will have to compare the two JSON formats by hand and apply migrations....

You could do it if you have a very primitive data structure - but it will be a default task where you will get dirty hands. Because the structure of the JSON in Elastic Search is optimized for search while the JSON in IWA_BusinessData is optimized for beeing perfectly serializable by a Java. Main differences: - elastic search JSON knows no java types. If you have an abstract type in your data, the concrete type that was serialized must be written into the JSON or the JVM does not know which type to instantiate while deserialization - elastic search JSON does not knows objects that are equally used multiple times within the same object tree. Means if you used for instance an instance of Person that is refered multiple times in the same root Business Data you have no way to load this data with the JVM and know that the objects are the same. - elastic search JSON stores arrays in different format. Deserializtion will fail in the JVM so no. You should better restore the data from a backup dump of your database.