Hi folks, I'd like to revisit the discussion around our versioning policy specifically for the Hadoop ecosystem and make sure we are aware of the implications.
As an example our policy today would have us on HBase 2.1 and I have reminders to address this. However, currently the versions of HBase in the major hadoop distros are: - Cloudera 5 on HBase 1.2 (Cloudera 6 is 2.1 but is only in beta) - Hortonworks HDP3 on HBase 2.0 (only recently released so we can assume is not widely adopted) - AWS EMR HBase on 1.4 On the versioning I think we might need a more nuanced approach to ensure that we target real communities of existing and potential users. Enterprise users need to stick to the supported versions in the distributions to maintain support contracts from the vendors. Should our versioning policy have more room to consider on a case by case basis? For Hadoop might we benefit from a strategy on which community of users Beam is targeting? (OT: I'm collecting some thoughts on what we might consider to target enterprise hadoop users - kerberos on all relevant IO, performance, leaking beyond encryption zones with temporary files etc) Thanks, Tim
