So, I'm assuming all this means I can safely remove expression, mvel, asm from my packaging requirements?
I like this idea BTW https://github.com/elasticsearch/elasticsearch/issues/4859 (at the bottom). On Saturday, July 26, 2014 8:40:30 AM UTC-4, Jörg Prante wrote: > > One ticket addressed the issue of this asm dependency, with the solution > to switch the scope to "provided" > > https://github.com/elasticsearch/elasticsearch/issues/4859 > > Then, Lucene expressions jar was removed as dependency when ES switched to > 4.7.0 > > > https://github.com/elasticsearch/elasticsearch/commit/30d7b8de2fa043bdca3ca55026aa74f06d404a76 > > The jar was reintroduced in > > > https://github.com/elasticsearch/elasticsearch/commit/64ab22816c1a6dfcd505406da5abef51f5434f49 > > with dependency scope "compile". Which looks like a regression... > > Jörg > > > > On Sat, Jul 26, 2014 at 2:26 PM, [email protected] <javascript:> < > [email protected] <javascript:>> wrote: > >> Mmmmhhh.... I just examined ES 1.3 dependencies because I did not >> remember any asm jars in them... >> >> I must correct myself, now I learned that Lucene expressions - a new >> script language - depend on asm 4.1, and MVEL is standalone. >> >> So my suggestion is at first, before deploying, decide what script >> language you want to use. Then, secondly, fix the dependencies if necessary: >> >> - If you want Lucene expressions, take care that asm 4.1 is also in your >> web app classpath => this might conflict with Wildfly 8.1 >> >> - If you want the default MVEL, it seems ok (the MVEL 2.2.0 packages show >> a shaded asm which prevents dependency collisions - gotcha) >> >> - Also groovy is ok, and the other script language plugins (which I have >> not examined) as long as they do not depend on asm jars. >> >> Jörg >> >> >> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ elasticsearch >> --- >> [INFO] org.elasticsearch:elasticsearch:jar:1.3.0 >> [INFO] +- org.hamcrest:hamcrest-all:jar:1.3:test >> [INFO] +- >> com.carrotsearch.randomizedtesting:randomizedtesting-runner:jar:2.1.2:test >> [INFO] | \- junit:junit:jar:4.10:test >> [INFO] +- org.apache.lucene:lucene-test-framework:jar:4.9.0:test >> [INFO] | +- com.carrotsearch.randomizedtesting:junit4-ant:jar:2.1.3:test >> [INFO] | \- org.apache.ant:ant:jar:1.8.2:test >> [INFO] +- org.apache.httpcomponents:httpclient:jar:4.3.1:test >> [INFO] | +- org.apache.httpcomponents:httpcore:jar:4.3:test >> [INFO] | +- commons-logging:commons-logging:jar:1.1.3:test >> [INFO] | \- commons-codec:commons-codec:jar:1.6:test >> [INFO] +- org.apache.lucene:lucene-core:jar:4.9.0:compile >> [INFO] +- org.apache.lucene:lucene-analyzers-common:jar:4.9.0:compile >> [INFO] +- org.apache.lucene:lucene-codecs:jar:4.9.0:compile >> [INFO] +- org.apache.lucene:lucene-queries:jar:4.9.0:compile >> [INFO] +- org.apache.lucene:lucene-memory:jar:4.9.0:compile >> [INFO] +- org.apache.lucene:lucene-highlighter:jar:4.9.0:compile >> [INFO] +- org.apache.lucene:lucene-queryparser:jar:4.9.0:compile >> [INFO] | \- org.apache.lucene:lucene-sandbox:jar:4.9.0:compile >> [INFO] +- org.apache.lucene:lucene-suggest:jar:4.9.0:compile >> [INFO] | \- org.apache.lucene:lucene-misc:jar:4.9.0:compile >> [INFO] +- org.apache.lucene:lucene-join:jar:4.9.0:compile >> [INFO] | \- org.apache.lucene:lucene-grouping:jar:4.9.0:compile >> [INFO] +- org.apache.lucene:lucene-spatial:jar:4.9.0:compile >> [INFO] +- org.apache.lucene:lucene-expressions:jar:4.9.0:compile >> [INFO] | +- org.antlr:antlr-runtime:jar:3.5:compile >> [INFO] | +- org.ow2.asm:asm:jar:4.1:compile >> [INFO] | \- org.ow2.asm:asm-commons:jar:4.1:compile >> [INFO] +- com.spatial4j:spatial4j:jar:0.4.1:compile >> [INFO] +- com.vividsolutions:jts:jar:1.13:compile >> [INFO] +- com.github.spullara.mustache.java:compiler:jar:0.8.13:compile >> [INFO] +- com.google.guava:guava:jar:17.0:compile >> [INFO] +- com.carrotsearch:hppc:jar:0.5.3:compile >> [INFO] +- joda-time:joda-time:jar:2.3:compile >> [INFO] +- org.joda:joda-convert:jar:1.2:compile >> [INFO] +- org.mvel:mvel2:jar:2.2.0.Final:compile >> [INFO] +- com.fasterxml.jackson.core:jackson-core:jar:2.4.1.1:compile >> [INFO] +- >> com.fasterxml.jackson.dataformat:jackson-dataformat-smile:jar:2.4.1:compile >> [INFO] +- >> com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:jar:2.4.1:compile >> [INFO] +- >> com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:2.4.1:compile >> [INFO] +- io.netty:netty:jar:3.9.1.Final:compile >> [INFO] +- com.ning:compress-lzf:jar:0.9.6:compile >> [INFO] +- com.tdunning:t-digest:jar:3.0:compile >> [INFO] +- org.codehaus.groovy:groovy-all:jar:2.3.2:compile >> [INFO] +- log4j:log4j:jar:1.2.17:compile >> [INFO] +- org.slf4j:slf4j-api:jar:1.6.2:compile >> [INFO] +- net.java.dev.jna:jna:jar:4.1.0:compile >> [INFO] \- org.fusesource:sigar:jar:1.6.4:compile >> >> >> >> >> >> On Sat, Jul 26, 2014 at 1:51 PM, John D. Ament <[email protected] >> <javascript:>> wrote: >> >>> Yeah, I know ASM is a PITA :-) >>> >>> At least in my app, I'm using hibernate and CXF. I don't use JAXB >>> annotations currently as my webservices are super simple (due to the system >>> that needs to consume them). So I might be OK. >>> >>> If I remove MVEL, is that all I need to remove? >>> >>> In my current use case, I'm planning to do an embedded runtime based on >>> WildFly, where the app server node can act as a data node. This is until >>> we need to start scaling bigger (we're currently only looking at a couple >>> dozen users on at any time). When we start to scale, my recommendation to >>> the infra team is to build out dedicated ES nodes and allow them to join >>> the app server cluster with the app servers eventually moving out of data >>> mode and into just client mode. I'm assuming that doing this will cause >>> the data nodes to pull in whatever data was held by the app servers. >>> >>> Thanks a lot for your help so far! >>> >>> John >>> >>> >>> On Saturday, July 26, 2014 4:37:33 AM UTC-4, Jörg Prante wrote: >>> >>>> ASM is a PITA, it is not backward compatible. >>>> >>>> IIRC Wildfly 8.1 uses ASM 3 for hibernate and in CXF for some JAXB >>>> annotations so as long as you do not use this in your web app classpath it >>>> seems doable from within Wildfly, but you get the deployment errors. >>>> >>>> As said, my preference would be to drop MVEL from ES. >>>> >>>> Just use an ES TransportClient from within Widlfly. In that case there >>>> is no longer the need for a script language. I suggest not to create a >>>> full >>>> ES node in a web app container, this has other downsides (think of heap >>>> memory). Then you can exclude MVEL and ASM from ES jars safely, and most >>>> other dependencies too, just keep the ES jar and Lucene core jar with the >>>> query builders, this is enough for TransportClient. >>>> >>>> Jörg >>>> >>>> >>>> >>>> On Sat, Jul 26, 2014 at 3:44 AM, John D. Ament <[email protected]> >>>> wrote: >>>> >>>>> I can try upgrading ASM locally to see if it works. I'm assuming it's >>>>> backwards compatible? >>>>> >>>>> >>>>> On Friday, July 25, 2014 3:06:13 AM UTC-4, Jörg Prante wrote: >>>>> >>>>>> As a side note, I run Wildfly 8.1 on Java 8. ASM 3 does not work with >>>>>> Java 8, so I wonder how things can work out at all, even without ES. If >>>>>> possible, ASM 3 should be replaced by ASM 5.0 >>>>>> >>>>>> Jörg >>>>>> >>>>>> >>>>>> On Fri, Jul 25, 2014 at 9:02 AM, [email protected] < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> You have two choices: >>>>>>> >>>>>>> - drop ASM and MVEL, switch to Groovy for scripting >>>>>>> >>>>>>> - use TransportClient to avoid ES-cluster-side services like >>>>>>> scripting in Wildfly deployment (this is how I do it currently) >>>>>>> >>>>>>> Jörg >>>>>>> >>>>>>> >>>>>>> On Fri, Jul 25, 2014 at 3:30 AM, John D. Ament <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi all >>>>>>>> >>>>>>>> I was tinkering a bit with ElasticSearch. I think my target >>>>>>>> runtime may end up being embedded, just based on our deployment model. >>>>>>>> Probably not a big deal to get multiple nodes talking to each other >>>>>>>> and no >>>>>>>> additional hardware to deploy. >>>>>>>> >>>>>>>> I was trying to start the application in WildFly 8.1. When I go to >>>>>>>> deploy, I get errors related to ASM. It turns out that ES 1.3 ships >>>>>>>> w/ ASM >>>>>>>> 4.1. WildFly uses ASM 3.3.1. Is it possible to run ES against this >>>>>>>> version of ASM? It would seem that the two versions not compatible. >>>>>>>> >>>>>>>> If there's an alternative to running it on WF 8.1, I would love to >>>>>>>> hear it. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> John >>>>>>>> >>>>>>>> -- >>>>>>>> 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/4908b733-bab >>>>>>>> c-41bf-a87f-39ebfaea1f94%40googlegroups.com >>>>>>>> <https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%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/6856b6aa-bfa5-42de-8922-8be6d57a3221% >>>>> 40googlegroups.com >>>>> <https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%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] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%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/24e74e93-ed4f-491c-b964-9e7a41662f9b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
