I agree with Itamar. I'm a recent Elasticsearch user and Sense made it easier for me to learn the query syntax. I recommend it to all ES beginners. I only learned of Marvel later.
+1 for keeping the Chrome plugin on the Web Store, perhaps with a disclaimer that it's incomplete and no longer maintained. -- Nick On Tue, Apr 1, 2014 at 10:51 AM, Itamar Syn-Hershko <[email protected]>wrote: > Boaz, > > Sense is a must-have tool for any developer playing with Elasticsearch, at > least in my opinion. I use it daily to quickly sketch and test modeling > ideas, or just to prove a point. This is also the first thing I ask my > customers to install whenever I give on-site consults. > > I'd ask you and Elasticsearch to continue releasing Sense as a chrome > plugin that we can install and use. Even if it gets updated less > frequently, it's still an awesome tool and 80% is better than nothing. > > You can't rely on having Marvel installed for using Sense - it's an > additional install step, and many remote staging/prod clusters don't have > it installed. Sense is really great as a client-side independent thing. > > You can quote me on that: working with Elasticsearch is not the same > without Sense available as a Chrome plugin. > > For your consideration, > > -- > > Itamar Syn-Hershko > http://code972.com | @synhershko <https://twitter.com/synhershko> > Freelance Developer & Consultant > Author of RavenDB in Action <http://manning.com/synhershko/> > > > On Tue, Apr 1, 2014 at 11:44 AM, Boaz Leskes <[email protected]> wrote: > >> Hi Tim, Ivan, >> >> Sense, the chrome extension, was started a hobby project of mine. I did >> it in my spare time - I actually started it to prove it can be done in a >> weekend ;). As you know Sense is part of Marvel now where it will be >> professionally developed and get way more time and love. The github repo is >> not maintained anymore and the code as published on GitHub will not be >> developed further. I've updated the readme to make that more clear. >> >> As Tim noted, the Chrome extension has known bugs and does not support >> all of 1.0's features (like Aggregations). Since bug fixes are all going >> forward in Marvel, I've decided to remove the plugin from the Chrome Web >> Store so new users will not have a bad initial experience. >> >> I (and many others) am always happy to answer any questions/issue regard >> Marvel on the mailing list. If you find any issue, please post it and it >> will be picked up. I know you both know this as we interacted before, but I >> wanted to say again for anyone else that might read this in the future. >> Cheers, >> Boaz >> >> On Friday, March 28, 2014 5:19:38 PM UTC+1, Ivan Brusic wrote: >>> >>> I would have suggested opening an issue on Github to clarify the >>> license, but issues are disabled on the repo. I agree that Sense is a >>> fantastic tool. I deploy apps using the Java API, but I formulate my >>> thoughts and queries beforehand with Sense. Beforehand I was just using >>> straight curl commands. >>> >>> Boaz is a regular on the mailing list, he probably will chime in soon. >>> >>> -- >>> Ivan >>> >>> >>> On Fri, Mar 28, 2014 at 8:40 AM, Tim S <[email protected]> wrote: >>> >>>> Yeah, I cloned it locally in case it disappears and it seems to work >>>> perfectly well standalone or as an elasticsearch plugin - IMO it doesn't >>>> really need to be a chrome extension. But I guess its usefulness if limited >>>> if dev has stopped and the auto-complete isn't kept up-to-date with the >>>> elasticsearch api. >>>> >>>> Also if I recommended my clients used it (which I would, because it's >>>> one of the better rest front ends for ES I've come across because of the >>>> auto-complete) then they'd want to know whether they were actually allowed >>>> to use it i.e. what licence it is. >>>> >>>> >>>> >>>> On Friday, March 28, 2014 2:50:04 PM UTC, Ivan Brusic wrote: >>>> >>>>> I just forked it i case it goes away. I haven't built a Chrome >>>>> extension in years. Let me re-figure out how to do it and update my fork >>>>> with build/local installation instructions. >>>>> >>>>> The lack of a license might be problematic since default copyright >>>>> provisions apply: http://choosealicense.com/no-license/ >>>>> >>>>> -- >>>>> Ivan >>>>> >>>>> >>>>> On Fri, Mar 28, 2014 at 1:37 AM, Tim S <[email protected]> wrote: >>>>> >>>>>> I notice that https://github.com/bleskes/sense has a message saying >>>>>> "The development of Sense has moved into Elasticsearch Marvel". >>>>>> >>>>>> Does this mean that no further development will happen on github? >>>>>> I.e. if the Marvel team find bugs in sense will the fixes be pushed to >>>>>> the >>>>>> sense on github, and if I create a pull request on github will my fix >>>>>> find >>>>>> its way into the version of sense included in Marvel? >>>>>> >>>>>> Regardless of the answer to the above, does the code on github have >>>>>> any kind of licence? Even without Marvel, sense is still a useful tool. >>>>>> >>>>>> Thanks. >>>>>> >>>>>> -- >>>>>> 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/381ca707-f29c-4b81-8e5b-957c1c02fe0a%40goo >>>>>> glegroups.com<https://groups.google.com/d/msgid/elasticsearch/381ca707-f29c-4b81-8e5b-957c1c02fe0a%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/a8c17fc2-0f74-4161-992f-0a3e77e7153b% >>>> 40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/a8c17fc2-0f74-4161-992f-0a3e77e7153b%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/a124cd7d-5466-4786-9e4b-935eb214566c%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/a124cd7d-5466-4786-9e4b-935eb214566c%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/CAHTr4ZsYDo0qzzBgfBKSXADr9vOQqp-YhoZTjRQ4iwsxGzDcxQ%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZsYDo0qzzBgfBKSXADr9vOQqp-YhoZTjRQ4iwsxGzDcxQ%40mail.gmail.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/CAH4ejsv_i5sraWh2vH4Dy-aJAQ0A5jALBPjzFJg3yyW6x2e%2BtA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
