Update callbacks do not use as_indexed_json about elasticsearch-rails

[palanglung]

+1
the changed_attributes should filtered as like as_indexed_json cause maybe not all fields are public and used for indexing.

[fcheung]

If we did want to make this work beyond trivial cases perhaps ES::Model should be asking the instance for updates rather than taking them out of changed attributes. There could always be a default implementation that just returned the changed attributes.

On the otherhand perhaps the pragmatic thing is to just write your own update_document if you have that need.

[samqiu]

Please see #5 .

[fcheung]

D'oh - I'm a dummy. Given that the conclusion has been reached that the library shouldn't be trying to do anything smart in this case, perhaps the documentation should reflect this?

[spodlecki]

+1 to document it's behavior in README. I had custom callbacks, and it would not update the serialized json field. The solution was to just use es.index_document on the models that have serialized fields versus update_document. Its a bit of a performance killer most likely, but it works and is only updated on a cron job every 20 mins.

[karmi]

@fcheung I'm still thinking whether we can somehow intercept the changes better, but I don't think so. It would be nice to check whether the model itself (and not the proxy) implements the as_indexed_method...

[karmi]

@fcheung Actually, the simple case was quite simple to solve, unless I'm missing something very obvious -- please check the linked commit.