Chris A.

> I think it'll be less of a maintenance nightmare to just split into V1 and V2 modules. I think this is what @bitemyapp and @MichaelXavier are leaning towards? No,...

> What does PIC stand for? Person in charge. > Can you elaborate on what you mean by "we support one set of versions in one module"? Do you mean...

@MHova if and when someone says they need 2.0-only support. For now the overlap seems to be mostly okay. Some documentation tweaks might help prevent nasty surprises.

> Amazon's brand new hosted ElasticSearch is only 1.x and I would be surprised if they added 2.0 support in the next few quarters or even this year. That's a...

> Though seriously, what is the benefit of a mutually compatible module? Avoiding unnecessary duplication when the overlap is 95% anyway. Identical types will be equal to each other, types/functions...

@MHova /cc @MichaelXavier I'm giving Xavier an opportunity to push back here. While that plan sounds good, this is the theorycrafting I said I wanted to avoid until we had...

@bermanjosh speaking for myself, (don't know what Michael is cooking up), I have no changes planned at this time so you should be fairly clear to get this done and...

@bermanjosh could you list the datatypes that need to change and provide a couple examples of before and after? I'm not saying a pure cutover isn't the right answer, but...

@lloucas-imvu First, my condolences. > This is rejected by elasticsearch. Which version?

> I understand that this is not a supported version. Seems weird that it would change between versions and not appear in any documentation. Boy are you in for a...