Models

[davidjairala]

No description provided.

[davidjairala]

TODO: update readme.

[jrichardlai]

do you need to symbolize_keys on column_defaults?

[jrichardlai]

Looks good I like it :)

[mnelson]

I think you might be able to just use ActiveModel::Model but it's been a while since I've used it.

[evantahler]

Philosophy Ramblings:

This is awesome. However, if you you able to save a new model and re-load it quickly, we know that it's very likely that ES will not yet have indexed the new object, and things like model.reload! or just finding the object again be likely to fail. This isn't anything different than how the tool worked before, but the ActiveRecord semantics (because folks are used to working with mySQL et al) might imply that you can think about model.save in the same way.

Since you are working with only one record here (as opposed to multi writes which you might use some of the other waistband sections for), you have the opportunity to enforce that when you call model.save, the next line really will have it available:

• You can ask the index for its refresh frequency and sleep that long after a save?
• You can do a while unreadable loop (with a 5s timeout) to try and read the object before moving on from the save method
• You can cache the object in some way?

Eh, these are all probably terrible ideas... never mind!

[davidjairala]

Well, reload! would work using the find method, which is not a search, so
it would not be affected by refresh shenanigans since when you have the id
it knows which node to grab it from.

On Sun, Feb 22, 2015 at 11:42 AM, Evan Tahler [email protected]
wrote:

Philosophy Ramblings:

This is awesome. However, if you you able to save a new model and re-load
it quickly, we know that it's very likely that ES will not yet have indexed
the new object, and things like model.reload! or just finding the object
again be likely to fail. This isn't anything different than how the tool
worked before, but the ActiveRecord semantics (because folks are used to
working with mySQL et al) might imply that you can think about model.save
in the same way.

Since you are working with only one record here (as opposed to multi
writes which you might use some of the other waistband sections for), you
have the opportunity to enforce that when you call model.save, the next
line really will have it available:

• You can ask the index for its refresh frequency and sleep that long
  after a save?
• You can do a while unreadable loop (with a 5s timeout) to try and
  read the object before moving on from the save method
• You can cache the object in some way?

Eh, these are all probably terrible ideas... never mind!

—
Reply to this email directly or view it on GitHub
#18 (comment).

Pablo Jairala |* TaskRabbit *| Staff Engineer

[evantahler]

Huh, I thought you always needed to wait for the refresh (even when loading by document ID).... Fancy!