Hi, thanks for starting this discussion: agreed on the need to release something soon! One word of caution though: it looks like media are picking up on this work with interest so I expect a good amount of people to try the first "preview" out; yet the expectations will probably be higher than usual. +1 to identify a MVP and to make it very clear what's not done yet, as we know that people won't easily forgive and some will not give us a second chance with a 5.7. Your list looks good; [BTW I thought that HSEARCH-2092 was very easy?]. You're all very welcome to mark things "blocker" when the user experience is not good, for example I just raised Emmanuel's feedback HSEARCH-2213 to blocker. After Beta1 we'll start to explicitly mark issues for 5.7, unless you feel the need to mark some already? I'd rather mark some as lower priority, and we all keep in mind that if you have time you should pick a higher-priority task, I just don't feel like moving low-hanging fruits out yet if there's a chance to implement some of these as well. Speaking of Beta1 .. I hope soon (10 days?) but that will have to wait on feature completeness of our list, we can do time-boxing for the next milestone but I think the major ones need to be all done, so no timeboxing for the specific Beta1, CR and Final. +1 for a quick CR & Final after Beta phase.. as you say, people don't really provide much feedback until it's "final tech preview" ;) Thanks, Sanne On 13 April 2016 at 14:54, Gunnar Morling <gunnar(a)hibernate.org&gt; wrote: > Hey, > > I'd like to achieve clarity and agreement on the scope of HSEARCH 5.6, the > first release with support for the Elasticsearch indexing backend. > > I suggest we limit ourselves to the essential things making the backend > actually usable and release it as a "technology preview" as of 5.6.0.Final. > Everything not needed for that goal I'd move to subsequent releases (5.7, > 6.0), the motivation being that we should not kill the vibe and deliver > something real soon. > > Some candidates for moving over I see: > > * "Define analyzers via the REST API (HSEARCH-2219 > <https://hibernate.atlassian.net/browse/HSEARCH-2219>)";: Users can create > the needed analyzers themselves > * "Consider using the fields feature of Elasticsearch for properties mapped > on several fields" (HSEARCH-2215 > <https://hibernate.atlassian.net/browse/HSEARCH-2215>): Seems scheduled as > a "reminder" only anways? > * "Use the Elasticsearch Scroll API when fetching large result sets" ( > HSEARCH-2128 <https://hibernate.atlassian.net/browse/HSEARCH-2128>): Seems > not strictly needed > * "Map the optimize() operation to Elasticsearch 'force merge' requests" ( > HSEARCH-2092 <https://hibernate.atlassian.net/browse/HSEARCH-2092>): Manual > requests possible as a work-around > * Likely some others > > Things we *should* do are most mapping-related issues, documentation and > apparent perf issues (massing indexing, avoid too frequent refreshing). > > The public interest in the subject seemed good, so I'd prefer if we can > ship a "Final" version soon in MVP-style. As it seems, a "final" tech > preview is less scary to people than an Alpha/Beta. Let's hone the bits it > in subsequent releases, rather than working on the first Final for a long > time. > > Any thoughts? > > --Gunnar > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev