Skip to content

Conversation

russcam
Copy link
Contributor

@russcam russcam commented Nov 3, 2016

Update Rest Api Specs to v2.4.1
Closes #2306

@russcam russcam added the v2.4.7 label Nov 3, 2016
Copy link
Member

@Mpdreamz Mpdreamz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets add some Get and Delete not found integrations tests that assert _index et all still get set too.

@russcam russcam force-pushed the fix/2.x-allow404s branch 2 times, most recently from 463fedb to d16ebcf Compare November 9, 2016 01:38
Update Rest Api Specs to v2.4.1
Closes #2306
@russcam
Copy link
Contributor Author

russcam commented Nov 9, 2016

Added integration tests for delete and get on non-existent documents.

@russcam russcam merged commit d16ebcf into 2.x Nov 9, 2016
@russcam russcam deleted the fix/2.x-allow404s branch November 24, 2016 07:45
@rdehuyss
Copy link
Contributor

rdehuyss commented Feb 6, 2017

Guys, we wanted to let you know that this breaks backwards compatibility. We just lost a lot of time due to this enhancement... Can these kind of changes be kept for major upgrades?

@Mpdreamz
Copy link
Member

Mpdreamz commented Feb 6, 2017

I'm sorry to hear @rdehuys we strive not to break bwc but I can see this being a big functional change.

should we

  1. Revert this and delist 2.4.7? Or would that be even worse.
  2. Keep this but with an obsolete warning on IsValid going forward.

Neither is pretty but I'd hate for others to lose time here too.

Cc @elastic/microsoft

@rdehuyss
Copy link
Contributor

rdehuyss commented Feb 6, 2017

We upgraded our part of the code, so all is fine now. Our test suite luckily failed so nothing went broken to production.

So, option 2 is fine for us!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants