Ok, so here is what I wanted to suggest: every query could have a "Validate & explain" link in the little dropdown:
<https://lh4.googleusercontent.com/-v9pBKj951ms/VAXr8S6VhwI/AAAAAAAAAHQ/byRJK0Ex5iA/s1600/Screenshot%2Bfrom%2B2014-09-02%2B18%3A06%3A37.png> Just under "Auto indent". And as you can guess, it call "POST /yolo/_validate/query?explain" with my query! This _validate/?explain endpoint is really a powerful tool to debug queries and I think it deserve more visibility. That's it :) Thank for you answer, Damien On Tuesday, September 2, 2014 5:54:26 PM UTC+2, Boaz Leskes wrote: > > > About Sense, it feel like a closed source software now. > > Yes, Sense is now part of Marvel, which is closed source. > > > Can we have an open bug tracker to suggest idea? > > We currently collect ideas and issues using this group. Would love to hear > it if you have a suggestion! > > > Cheers, > Boaz > > > On Tue, Sep 2, 2014 at 5:51 PM, Damien Alexandre <[email protected] > <javascript:>> wrote: > >> About Sense, it feel like a closed source software now. >> >> Can we have an open bug tracker to suggest idea? >> or even better, open the code to accept pull requests? >> >> >> Also, >> this is a great example of why one should always set a license when >> publishing code :P >> >> Damien >> >> >> On Wednesday, April 30, 2014 10:24:19 PM UTC+2, @mromagnoli wrote: >>> >>> Yeah, maybe you are right. Anyway i have installed Marvel, and make a >>> bookmark in Chrome with the URL to Sense. >>> >>> Perhaps I cried in advance ;P >>> >>> El miércoles, 30 de abril de 2014 17:19:36 UTC-3, Ivan Brusic escribió: >>>> >>>> Must is a strong word. I highlighted some alternatives earlier. >>>> On Apr 30, 2014 1:01 PM, "@mromagnoli" <[email protected]> wrote: >>>> >>>>> Agree 100%. Sense must return to Chrome Store! >>>>> >>>>> El martes, 29 de abril de 2014 11:52:49 UTC-3, Joshua Worden escribió: >>>>>> >>>>>> Would love to see this return to the chrome store. Was rather >>>>>> surprised to see it gone when getting another developer started working >>>>>> with elasticsearch. Even if it was buggy, it was the best way to get >>>>>> started. >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "elasticsearch" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web visit https://groups.google.com/d/ >>>>> msgid/elasticsearch/98d89444-f75c-4f50-aece-6e55337c868d% >>>>> 40googlegroups.com >>>>> <https://groups.google.com/d/msgid/elasticsearch/98d89444-f75c-4f50-aece-6e55337c868d%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "elasticsearch" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/elasticsearch/rPS1duxMzyM/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/116782df-a22e-4723-b460-319740e40d5a%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/116782df-a22e-4723-b460-319740e40d5a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1b4294c3-9b4c-4490-b301-2d5d7da1620d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
