What this essentially does is limit a developer's options I went to my boss, and laid out the plans for implementing ES, and told them there was no cost, open-source
Now i have to go back and explain we need licensing on our production VM if we need to use sense on that VM, we don't need marvel, its an internal app to a department of 100 or less users If i originally had laid out a plan with costs/licensing agreements, it would have had to go to a guidance council for approval of the license, department cost approval, and more than likely would have been ruled out as an option , and gone with SOLR instead -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Sense-on-github-abandoned-tp4052988p4054272.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1397659439498-4054272.post%40n3.nabble.com. For more options, visit https://groups.google.com/d/optout.
