5 ms·
From the announcement: "You should consider the initial code to be at an alpha stage — it is not complete, not thoroughly tested, and not suitable for productio
by phd514 5y ago
From the announcement: "You should consider the initial code to be at an alpha stage — it is not complete, not thoroughly tested, and not suitable for production use. We are planning to release a beta in the next few weeks, and expect it to stabilize and be ready for production by early summer (mid-2021)."
Given that Amazon announced the fork in January and they don't expect it to be production-ready until summer, I'm guessing they've underestimated the amount of work required to package and distribute a product as complex as Elasticsearch. Given that, I doubt they will be well-equipped to keep pace with new feature development.
- lornajane 5y agoI'm not sure I agree with that assessment. Now that the fork is publicly available, others can contribute to get it ready, which wasn't possible until now.
- phd514 5y agoYes, others can contribute, but significant feature development on large-scale OSS projects tends to be driven by developers paid to work on the project full-time and coordinated by an organized steering committee with clear governance (or company if the product is owned by a single company). I don't see any of that in place for OpenSearch and getting that all started up is not at all a trivial endeavor.
- busterarm 5y agoGiven how poorly of a job Elastic themselves did with keeping the full ecosystem of tools working in lockstep for YEARS, I'm sure Amazon will do fine. I remember all through Elasticsearch 5 where none of their packaged Kibana dashboards flippin' worked.
- colechristensen 5y agoI would assume they’re doing more than just packaging. A beginning is the time for taking the most delicate care that the balances are correct
- fastball 5y ago6 months from start to prod is... not bad at all? You must be a wizard programmer if that is your typical turnaround time. I don't remember AWS saying something like "it will be ready in weeks" in Jan...
- deleted 5y ago[deleted]
- acdha 5y agoI would question the assumption that this is “not suitable for production use” means “everything is broken and we're way behind” rather than, say, “we are being extremely conservative because our customers will expect support as soon as we say it's production ready and we need to test every upgrade scenario for our large number of existing customers”. The AWS-managed ElasticSearch seems to be pretty popular and I would expect them to be as conservative about new offerings as they are with, say, RDS.
- z77dj3kl 5y agoThe fork announcement was announced as a response to the Elastic stuff. I don't think they made any predictions about when it'd be ready in that blog post, so I'm not sure why they would've underestimated anything?
- retzkek 5y ago> they've underestimated the amount of work required to package and distribute a product as complex as Elasticsearch The bulk of the work thus far has been to strip out the non-OSS components ("X-pack") and the many references to it, nothing to do with packaging, distributing, or even maintaining and developing features. https://discuss.opendistrocommunity.dev/t/preparing-opensearch-and-opensearch-dashboards-for-release/5567 https://discuss.opendistrocommunity.dev/t/preparing-opensear...
- zo1 5y agoI for one will be happy when those are taken out. So many headaches trying to get bloated Kibana to start as a docker container before realizing that some random x-pack-disable flag needs to be set for it to start without a random error.