I think it should be fine to use 6.x elasticsearch. Willem Jiang
Twitter: willemjiang Weibo: 姜宁willem On Wed, Jul 17, 2019 at 11:12 AM Zhang Lei <zhang_...@boco.com.cn> wrote: > > I want to use spring-data-elasticsearch[1]. spring-data-elasticsearch 3.1.x > compatibility elasticsearch 6.2.2 > > [1] https://github.com/spring-projects/spring-data-elasticsearch > <https://github.com/spring-projects/spring-data-elasticsearch> > > > > 在 2019年7月17日，上午11:00，Zheng Feng <zh.f...@gmail.com> 写道： > > > > +1 and which version of the ElasticSearch should we use ? > > > > Willem Jiang <willem.ji...@gmail.com> 于2019年7月17日周三 上午10:49写道： > > > >> big +1 on it. > >> > >> I think we need to let the user know about this change, as this state > >> machine part is in experimental status, I'm proposing that we list > >> the features which we want do in this release cycle at the end of this > >> August to make sure we can provide a basic runnable Saga coordinator > >> on top of state machine solution. > >> > >> > >> Willem Jiang > >> > >> Twitter: willemjiang > >> Weibo: 姜宁willem > >> > >> On Wed, Jul 17, 2019 at 10:26 AM Zhang Lei <zhang_...@boco.com.cn> wrote: > >>> > >>> Hi, all > >>> > >>> After reimplementing Saga with a state machine, we no longer need to > >> perform complex table scans, so we can use ElasticSearch to persist > >> transaction data. And use the ElasticSearch RESTful API to provide external > >> query capabilities for terminating transactions. > >>> > >>> 1. Improve the performance of Alpha data persistence > >>> 2. This will reduce the performance impact of the query on Alpha > >>> 3. Users extend their monitoring capabilities based on ElasticSearch > >> rich RESTful API > >>> > >>> Lei Zhang > >> >
