tag:old.nabble.com,2006:forum-44
Nabble - Lucene
2009-12-23T15:36:45Z
The <a href="http://lucene.apache.org/" target="_top" rel="nofollow">Apache Lucene</a> project develops open-source search software In a variety of languages. The flagship sub-project is "Lucene - Java", many questions people have about using the "Lucene Library" can be best addressed on the <a href="http://www.nabble.com/Lucene---Java-Users-f45.html" target="_top">java-users mailing list</a>
tag:old.nabble.com,2006:post-26908849
Re: Field Collapsing - disable cache
2009-12-23T15:36:45Z
2009-12-23T15:36:45Z
rob-249
<br>Here's the sorlconfig, with a few fields removed from the request (which shouldn't make any difference)
<br><br><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br><br>perhaps an old solrconfig to start with? tho it came no later than a 1.3 standard config file.
<br><br><br><br><br>On Wed 23/12/09 21:33 , Martijn v Groningen <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26908849&i=0" target="_top" rel="nofollow">martijn.is.hier@...</a>> wrote:
<br><div class='shrinkable-quote'><br>> How have you configured field collapsing?
<br>> I have field collapsing configured without caching like this:
<br>> and with caching like this:
<br>> In both situations I don't get NPE. Also the line (in the patch)
<br>> where
<br>> the exceptions occurs seems unlikely for a NPE.
<br>> if (fieldCollapseCache != null) {
<br>> fieldCollapseCache.put(currentCacheKey, new CacheValue(result,
<br>> collectors, collapseContext)); // line 276
<br>> }
<br>> Does the exception occur immediately after the first search?
<br>> Martijn
<br>> 2009/12/23 :
<br>> >
<br>> > Still seeing the same error when trying to comment out the
<br>> fieldCollapsing block, or even just the fieldCollapseCache block
<br>> inside it to disable the cache.
<br>> >
<br>> > fresh trunk and latest patch.
<br>> >
<br>> >
<br>> >
<br>> > message null java.lang.NullPointerException at
<br>> org.apache.solr.search.fieldcollapse.AbstractDocumentCollapser.createDocume
<br>> ntCollapseResult(AbstractDocumentCollapser.java:276)at
<br>> org.apache.solr.search.fieldcollapse.AbstractDocumentCollapser.executeColla
<br>> pse(AbstractDocumentCollapser.java:249)at
<br>> org.apache.solr.search.fieldcollapse.AbstractDocumentCollapser.collapse(Abs
<br>> tractDocumentCollapser.java:172)at
<br>> org.apache.solr.handler.component.CollapseComponent.doProcess(CollapseCompo
<br>> nent.java:173)at
<br>> org.apache.solr.handler.component.CollapseComponent.process(CollapseCompone
<br>> nt.java:127)at
<br>> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHan
<br>> dler.java:195)at
<br>> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase
<br>> .java:131)at org.apache.solr.core.SolrCore.execute(SolrCore.java:1316) at
<br>> org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:
<br>> 336)at
<br>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java
<br>> :239)at
<br>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicatio
<br>> nFilterChain.java:215)at
<br>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterC
<br>> hain.java:188)at
<br>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.j
<br>> ava:210)at
<br>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.j
<br>> ava:172)at
<br>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:12
<br>> 7)at
<br>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:11
<br>> 7)at
<br>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.jav
<br>> a:108)at
<br>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
<br>> at
<br>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
<br>> at
<br>> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.process
<br>> Connection(Http11BaseProtocol.java:665)at
<br>> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.ja
<br>> va:528)at
<br>> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerW
<br>> orkerThread.java:81)at
<br>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.ja
<br>> va:685)at java.lang.Thread.run(Thread.java:636)
<br>> >
<br>> >
<br>> >
<br>> >
<br>> >
<br>> >
<br>> >
<br>> > On Wed 23/12/09 13:26 , wrote:
<br>> >
<br>> >> Thanks, that latest update to the patch works fine now.
<br>> >> On Wed 23/12/09 13:13 , Martijn v Groningen wrote:
<br>> >> > Latest SOLR-236.patch is for the trunk, if have updated the
<br>> latest
<br>> >> > patch so it should patch now without conflicts. If I remember
<br>> >> > correctly the latest field-collapse-5.patch should work for
<br>> 1.4,
<br>> >> but
<br>> >> > it doesn't for the trunk.
<br>> >> > 2009/12/23 :
<br>> >> > >
<br>> >> > > Sorry, that was when trying to patch the 1.4 branch
<br>> >> > >
<br>> >> > > attempting to patch the trunk gives...
<br>> >> > >
<br>> >> > > patching file
<br>> src/test/test-files/fieldcollapse/testResponse.xml
<br>> >> > > patching file
<br>> >> > src/test/org/apache/solr/BaseDistributedSearchTestCase.java
<br>> >> > > Hunk #2 FAILED at 502.
<br>> >> > > 1 out of 2 hunks FAILED -- saving rejects to file
<br>> >> > src/test/org/apache/solr/BaseDistributedSearchTestCase.java.rej
<br>> >> > > patching file
<br>> >> >
<br>> >>
<br>> src/test/org/apache/solr/search/fieldcollapse/FieldCollapsingIntegrationTes
<br>> >> > t.java>
<br>> >> > >
<br>> >> > > btw, when is trunk actually updated?
<br>> >> > >
<br>> >> > >
<br>> >> > >
<br>> >> > >
<br>> >> > >
<br>> >> > > On Wed 23/12/09 11:53 , wrote:
<br>> >> > >
<br>> >> > >> I'm currently trying to patch aginst trunk, using
<br>> >> SOLR-236.patch
<br>> >> > >> from 18/12/2009 but getting the following error...
<br>> >> > >> [ solr]$ patch -p0 < SOLR-236.patch
<br>> >> > >> patching file
<br>> >> > >> src/test/test-files/solr/conf/solrconfig-fieldcollapse.xml
<br>> >> > >> patching file
<br>> >> > src/test/test-files/solr/conf/schema-fieldcollapse.xml
<br>> >> > >> patching file src/test/test-files/solr/conf/solrconfig.xml
<br>> >> > >> patching file
<br>> >> src/test/test-files/fieldcollapse/testResponse.xml
<br>> >> > >> can't find file to patch at input line 787
<br>> >> > >> Perhaps you used the wrong -p or --strip option?
<br>> >> > >> The text leading up to this was:
<br>> >> > >> --------------------------
<br>> >> > >> |
<br>> >> > >> |Property changes on:
<br>> >> > >> src/test/test-files/fieldcollapse/testResponse.xml
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> |___________________________________________________________________
<br>> >> > >> |Added: svn:keywords
<br>> >> > >> | + Date Author Id Revision HeadURL
<br>> >> > >> |Added: svn:eol-style
<br>> >> > >> | + native
<br>> >> > >> |
<br>> >> > >> |Index:
<br>> >> > src/test/org/apache/solr/BaseDistributedSearchTestCase.java
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> |===================================================================
<br>> >> > >> |---
<br>> >> src/test/org/apache/solr/BaseDistributedSearchTestCase.java
<br>> >> > >> (revision 891214)
<br>> >> > >> |+++
<br>> >> src/test/org/apache/solr/BaseDistributedSearchTestCase.java
<br>> >> > >> (working copy)
<br>> >> > >> --------------------------
<br>> >> > >> File to patch:
<br>> >> > >> any suggestions, or should i checkout the 1.4 branch
<br>> instead?
<br>> >> > >> can't remember what i did last time to get
<br>> >> field-collapse-5.patch
<br>> >> > >> working successfully.
<br>> >> > >> On Tue 22/12/09 22:43 , Lance Norskog wrote:
<br>> >> > >> > To avoid this possible bug, you could change the cache to
<br>> >> only
<br>> >> > >> have a
<br>> >> > >> > few entries.
<br>> >> > >> > On Tue, Dec 22, 2009 at 6:34 AM, Martijn v Groningen
<br>> >> > >> > wrote:
<br>> >> > >> > > In the latest patch some changes where made on the
<br>> >> > configuration
<br>> >> > >> > side,
<br>> >> > >> > > but if you add the CollapseComponent to the conf no
<br>> field
<br>> >> > >> collapse
<br>> >> > >> > > cache should be enabled. If not let me know.
<br>> >> > >> > >
<br>> >> > >> > > Martijn
<br>> >> > >> > >
<br>> >> > >> > > 2009/12/22 :
<br>> >> > >> > >>
<br>> >> > >> > >>
<br>> >> > >> > >>
<br>> >> > >> > >>
<br>> >> > >> > >>
<br>> >> > >> > >> On Tue 22/12/09 12:28 , Martijn v Groningen wrote:
<br>> >> > >> > >>
<br>> >> > >> > >>> Hi Rob,
<br>> >> > >> > >>> What patch are you actually using from SOLR-236?
<br>> >> > >> > >>> Martijn
<br>> >> > >> > >>> 2009/12/22 :
<br>> >> > >> > >>> > I've tried both, the whole fieldCollapsing tag, and
<br>> >> just
<br>> >> > the
<br>> >> > >> > >>> > fieldCollapseCache tag inside it.
<br>> >> > >> > >>> > both cause error.
<br>> >> > >> > >>> > I guess I can just set size, initialSize, and
<br>> >> > >> > autowarmCount
<br>> >> > >> > >>> to 0 ??
<br>> >> > >> > >>> > On Tue 22/12/09 11:17 , Toby Cole wrote:Which
<br>> elements
<br>> >> > did
<br>> >> > >> > you
<br>> >> > >> > >>> > comment out? It could be the case that you need
<br>> >> > >> > >>> > to get rid of the entire fieldCollapsing element,
<br>> not
<br>> >> > just
<br>> >> > >> the
<br>> >> > >> > >>> > fieldCollapsingCache element.
<br>> >> > >> > >>> > (Disclaimer: I've not used field collapsing in anger
<br>> >> > before
<br>> >> > >> :)
<br>> >> > >> > >>> > Toby.
<br>> >> > >> > >>> >
<br>> >> > >> > >>> > On 22 Dec 2009, at 11:09, wrote:
<br>> >> > >> > >>> >
<br>> >> > >> > >>> >> That's what I assumed, but I'm getting the
<br>> following
<br>> >> > error
<br>> >> > >> > with
<br>> >> > >> > >>> it
<br>> >> > >> > >>> >> commented out....
<br>> >> > >> > >>> >> MESSAGE null java.lang.NullPointerException at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >> .solr
<br>> >> > >> > >>> >> .search
<br>> >> > >> > >>> >> .fieldcollapse
<br>> >> > >> > >>> >> .AbstractDocumentCollapser
<br>> >> > >> > >>> >>
<br>> >> > >> >
<br>> >> >
<br>> .createDocumentCollapseResult(AbstractDocumentCollapser.java:276)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >> .solr
<br>> >> > >> > >>> >> .search
<br>> >> > >> > >>> >> .fieldcollapse
<br>> >> > >> > >>> >> .AbstractDocumentCollapser
<br>> >> > >> > >>> >>
<br>> .executeCollapse(AbstractDocumentCollapser.java:249)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >> .solr
<br>> >> > >> > >>> >> .search
<br>> >> > >> > >>> >> .fieldcollapse
<br>> >> > >> > >>> >>
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .AbstractDocumentCollapser.collapse(AbstractDocumentCollapser.java:
<br>> >> > >> > >>> >
<br>> >> > >> > >>> >> 172)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >> .solr
<br>> >> > >> > >>> >> .handler
<br>> >> > >> > >>> >>
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> >
<br>> .component.CollapseComponent.doProcess(CollapseComponent.java:173)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >> .solr
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .handler.component.CollapseComponent.process(CollapseComponent.java:
<br>> >> > >> > >>> >> 127)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >> .solr
<br>> >> > >> > >>> >> .handler
<br>> >> > >> > >>> >>
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> >
<br>> .component.SearchHandler.handleRequestBody(SearchHandler.java:195)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >> .solr
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:131)
<br>> >> > >> > >>> >> at
<br>> >> > >> org.apache.solr.core.SolrCore.execute(SolrCore.java:1316)
<br>> >> > >> > at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:336)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:239)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >> .catalina
<br>> >> > >> > >>> >> .core
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:
<br>> >> > >> > >>> >
<br>> >> > >> > >>> >> 215)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >> .catalina
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:
<br>> >> > >> > >>> >
<br>> >> > >> > >>> >> 210)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .catalina.core.StandardContextValve.invoke(StandardContextValve.java:
<br>> >> > >> > >>> >
<br>> >> > >> > >>> >> 172)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >>
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >>
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >>
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:
<br>> >> > >> > >>> >
<br>> >> > >> > >>> >> 108)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:
<br>> >> > >> > >>> >> 151)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >>
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .apache.coyote.http11.Http11Processor.process(Http11Processor.java:
<br>> >> > >> > >>> >
<br>> >> > >> > >>> >> 870)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org.apache.coyote.http11.Http11BaseProtocol
<br>> >> > >> > >>> >>
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> $Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:
<br>> >> > >> > >>> >
<br>> >> > >> > >>> >> 665)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:
<br>> >> > >> > >>> >> 528)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org
<br>> >> > >> > >>> >> .apache
<br>> >> > >> > >>> >> .tomcat
<br>> >> > >> > >>> >> .util
<br>> >> > >> > >>> >> .net
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> .LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
<br>> >> > >> > >>> >> at
<br>> >> > >> > >>> >> org.apache.tomcat.util.threads.ThreadPool
<br>> >> > >> > >>> >> $ControlRunnable.run(ThreadPool.java:685)
<br>> >> > >> > >>> >> at java.lang.Thread.run(Thread.java:636)
<br>> >> > >> > >>> >> On Tue 22/12/09 11:02 , Toby Cole wrote:If you
<br>> take
<br>> >> out
<br>> >> > >> the
<br>> >> > >> > >>> >> fieldCollapsing/fieldCollapseCache element in your
<br>> >> > >> > >>> >> config the fieldcollapse component will not use a
<br>> >> cache.
<br>> >> > >> > >>> >> From
<br>> >> > >> <a href="http://wiki.apache.org/solr/FieldCollapsing%2523line-63" target="_top" rel="nofollow">http://wiki.apache.org/solr/FieldCollapsing%2523line-63</a><br>> >> > >> > [2]"
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> target="_blank"><a href="http://wiki.apache.org/solr/FieldCollapsing%23line-63" target="_top" rel="nofollow">http://wiki.apache.org/solr/FieldCollapsing%23line-63</a><br>> >> > >> > >>> > [1]"
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> target="_blank"><a href="http://wiki.apache.org/solr/FieldCollapsing%23line-63" target="_top" rel="nofollow">http://wiki.apache.org/solr/FieldCollapsing%23line-63</a><br>> >> > >> > >>> > [3]"
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> target="_blank"><a href="http://wiki.apache.org/solr/FieldCollapsing#line-63" target="_top" rel="nofollow">http://wiki.apache.org/solr/FieldCollapsing#line-63</a><br>> >> > >> > >>> >> "If the field collapse cache is not configured then
<br>> >> the
<br>> >> > >> field
<br>> >> > >> > >>> >> collapse logic will not be cached."
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >> Regards, Toby.
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >> On 22 Dec 2009, at 10:56, wrote:
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >>> my
<br>> >> > >> > >>> >>> solconfig can be seen at
<br>> >> > >> > >>> > <a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a> [4]"
<br>> >> > >> > >>> >
<br>> >> > target="_blank"><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>> >> > >> > >>> >> [3]"
<br>> >> > >> > target="_blank"><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>> >> > >> > >>> > [5]"
<br>> >> > >> > target="_blank"><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>> >> > >> > >>> >>> [1]
<br>> >> > >> > >>> >>> On Tue 22/12/09 10:51 , wrote:Is
<br>> >> > >> > >>> >>> it possible to disable the field collapsing cache?
<br>> >> I'm
<br>> >> > >> > trying
<br>> >> > >> > >>> to
<br>> >> > >> > >>> >>> perform some speed tests, and have managed to
<br>> comment
<br>> >> > out
<br>> >> > >> > the
<br>> >> > >> > >>> >> filter,
<br>> >> > >> > >>> >>> queryResult, and document caches successfully.
<br>> >> > >> > >>> >>>
<br>> >> > >> > >>> >>> on 1.5
<br>> >> > >> > >>> >>> ...
<br>> >> > >> > >>> >>> ...
<br>> >> > >> > >>> >>> collapse
<br>> >> > >> > >>> >>>
<br>> >> > >> > >>> >>> facet
<br>> >> > >> > >>> >>>
<br>> >> > >> > >>> >>> tvComponent
<br>> >> > >> > >>> >>> ...
<br>> >> > >> > >>> >>> -------------------------
<br>> >> > >> > >>> >>> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>> >> [6]"
<br>> >> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [5]"
<br>> >> > >> > >>> >> target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [7]"
<br>> >> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [2]"
<br>> >> > >> > >>> >>> target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [8]"
<br>> >> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [6]"
<br>> >> > >> > >>> >> target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [9]"
<br>> >> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>> >> > >> > >>> >>> -------------------------
<br>> >> > >> > >>> >>> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>> >> [10]"
<br>> >> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [7]"
<br>> >> > >> > >>> >> target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [11]"
<br>> >> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>> >> > >> > >>> >>>
<br>> >> > >> > >>> >>> Links:
<br>> >> > >> > >>> >>> ------
<br>> >> > >> > >>> >>> [1] <a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>> [12]"
<br>> >> > >> > >>> >
<br>> >> > target="_blank"><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>> >> > >> > [8]"
<br>> >> > >> > >>> >>
<br>> >> > target="_blank"><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>> >> > >> > [13]"
<br>> >> > >> > >>> >
<br>> >> > target="_blank"><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>> >> > >> > >>> >>> [2]
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> <a href="http://mail.intelcompute.com/parse.php%253Fredirect%253D%2526lt%253Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%253Fredirect%253D%2526lt%253Ba</a><br>> >> > >> > >>> > [14]"
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> target="_blank"><a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3</a><br>> >> > >> > >>> Ba>> [9]"
<br>> >> > >> > >>> >>
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> target="_blank"><a href="http://mail.intelcompute.com/parse.php%3Fredirect%3Dhttp://" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3Dhttp://</a><br>> >> > >> > >>> blogs.semantico.com/discovery-blog/> [15]"
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=http://blog" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=http://blog</a><br>> >> > >> > >>> s.semantico.com/discovery-blog/> [16]
<br>> >> > >> > >>> >> -------------------------
<br>> >> > >> > >>> >> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>> >> [17]"
<br>> >> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>> >> > >> > >>> >>
<br>> >> > >> > >>> >> Links:
<br>> >> > >> > >>> >> ------
<br>> >> > >> > >>> >> [1]
<br>> >> > >> >
<br>> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>> >> > >> > >>> > [18]"
<br>> >> > >> > >>> >
<br>> >> > >> >
<br>> >> >
<br>> target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>> >> > >> > >>> [3]
<br>> >> > >> > >>> >
<br>> >> > >>
<br>> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>> >> > >> > >>> [19]"
<br>> >> > >> > >>> >
<br>> >> > >> >
<br>> >> >
<br>> target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>> >> > >> > >>> [5]
<br>> >> > >> > >>> >
<br>> >> > >>
<br>> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>> >> > >> > >>> [20]"
<br>> >> > >> > >>> >
<br>> >> > >> >
<br>> >> >
<br>> target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>> >> > >> > >>> [6]
<br>> >> > >> > >>> >
<br>> >> > >>
<br>> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>> >> > >> > >>> [21]"
<br>> >> > >> > >>> >
<br>> >> > >> >
<br>> >> >
<br>> target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>> >> > >> > >>> [7]
<br>> >> > >> > >>> >
<br>> >> > >>
<br>> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>> >> > >> > >>> [22]"
<br>> >> > >> > >>> >
<br>> >> > >> >
<br>> >> >
<br>> target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>> >> > >> > >>> [8]
<br>> >> > >> > >>> >
<br>> >> > >>
<br>> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>> >> > >> > >>> [23]"
<br>> >> > >> > >>> >
<br>> >> > >> >
<br>> >> >
<br>> target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>> >> > >> > >>> [9]
<br>> >> > >> > >>> >
<br>> >> > >>
<br>> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>> >> > >> > >>> [24]"
<br>> >> > >> > >>> >
<br>> >> > >> >
<br>> >> >
<br>> target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>> >> > >> > >>> [10]
<br>> >> > >> > >>> >
<br>> >> > >>
<br>> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>> >> > >> > >>> [25]"
<br>> >> > >> > >>> >
<br>> >> > >> > >>>
<br>> >> > >> >
<br>> >> > >>
<br>> >> >
<br>> >>
<br>> target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=http://blog" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=http://blog</a><br>> >> > >> > >>> s.semantico.com/discovery-blog/>
<br>> >> -------------------------
<br>> >> > >> > >>> > Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>> >> > >> > >>> >
<br>> >> > >> > >>> > Links:
<br>> >> > >> > >>> > ------
<br>> >> > >> > >>> > [2] <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>> >> [3]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [4]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [5]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [6]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [7]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [8]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [9]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [10]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [11]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [12]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [13]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [14]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [15]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [16]
<br>> >> > >> > >>> <a href="http://blogs.semantico.com/discovery-blog/" target="_top" rel="nofollow">http://blogs.semantico.com/discovery-blog/</a><br>> >> > >> > >>> > [17]
<br>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>> >> > [18]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [19]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [20]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [21]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [22]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [23]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [24]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [25]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [27]
<br>> >> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>> >> > >> > >>> --
<br>> >> > >> > >>> Met vriendelijke groet,
<br>> >> > >> > >>> Martijn van Groningen
<br>> >> > >> > >>>
<br>> >> > >> > >>>
<br>> >> > >> > >> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>> >> > >> > >>
<br>> >> > >> > >
<br>> >> > >> > >
<br>> >> > >> > >
<br>> >> > >> > > --
<br>> >> > >> > > Met vriendelijke groet,
<br>> >> > >> > >
<br>> >> > >> > > Martijn van Groningen
<br>> >> > >> > >
<br>> >> > >> > --
<br>> >> > >> > Lance Norskog
<br>> >> > >> >
<br>> >> > >> >
<br>> >> > >> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>> >> > >>
<br>> >> > >>
<br>> >> > > Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>> >> > >
<br>> >> > --
<br>> >> > Met vriendelijke groet,
<br>> >> > Martijn van Groningen
<br>> >> >
<br>> >> >
<br>> >> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>> >>
<br>> >>
<br>> > Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>> >
<br>> --
<br>> Met vriendelijke groet,
<br>> Martijn van Groningen
<br>>
<br>>
</div>Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br><p>From forum: <a href="http://old.nabble.com/Solr---User-f14480.html" embed="fixTarget[14480]" target="_top" >Solr - User</a></p>
tag:old.nabble.com,2006:post-26908782
[jira] Resolved: (LUCENE-2179) CharArraySet.clear()
2009-12-23T15:27:29Z
2009-12-23T15:27:29Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/jira/browse/LUCENE-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/LUCENE-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ]
<br><br>Uwe Schindler resolved LUCENE-2179.
<br>-----------------------------------
<br><br> Resolution: Fixed
<br> Lucene Fields: [New, Patch Available] (was: [New])
<br><br>Committed revision: 893655
<br><div class='shrinkable-quote'><br>> CharArraySet.clear()
<br>> --------------------
<br>>
<br>> Key: LUCENE-2179
<br>> URL: <a href="https://issues.apache.org/jira/browse/LUCENE-2179" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/LUCENE-2179</a><br>> Project: Lucene - Java
<br>> Issue Type: Improvement
<br>> Components: Analysis
<br>> Reporter: Robert Muir
<br>> Assignee: Uwe Schindler
<br>> Priority: Minor
<br>> Fix For: 3.1
<br>>
<br>> Attachments: LUCENE-2179.patch
<br>>
<br>>
<br>> I needed CharArraySet.clear() for something I was working on in Solr in a tokenstream.
<br>> instead I ended up using CharArrayMap<Boolean> because it supported .clear()
<br>> it would be better to use a set though, currently it will throw UOE for .clear() because AbstractSet will call iterator.remove() which throws UOE.
<br>> In Solr, the very similar CharArrayMap.clear() looks like this:
<br>> {code}
<br>> @Override
<br>> public void clear() {
<br>> count = 0;
<br>> Arrays.fill(keys,null);
<br>> Arrays.fill(values,null);
<br>> }
<br>> {code}
<br>> I think we can do a similar thing as long as we throw UOE for the UnmodifiableCharArraySet
<br>> will submit a patch later tonight (unless someone is bored and has nothing better to do)
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26908782&i=0" target="_top" rel="nofollow">java-dev-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26908782&i=1" target="_top" rel="nofollow">java-dev-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/Lucene---Java-Developer-f46.html" embed="fixTarget[46]" target="_top" >Lucene - Java Developer</a></p>
tag:old.nabble.com,2006:post-26908783
[jira] Resolved: (LUCENE-2169) Speedup of CharArraySet#copy if a CharArraySet instance is passed to copy.
2009-12-23T15:27:29Z
2009-12-23T15:27:29Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/jira/browse/LUCENE-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/LUCENE-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ]
<br><br>Uwe Schindler resolved LUCENE-2169.
<br>-----------------------------------
<br><br> Resolution: Fixed
<br> Lucene Fields: [New, Patch Available] (was: [New])
<br><br>Committed revision: 893655
<br><div class='shrinkable-quote'><br>> Speedup of CharArraySet#copy if a CharArraySet instance is passed to copy.
<br>> --------------------------------------------------------------------------
<br>>
<br>> Key: LUCENE-2169
<br>> URL: <a href="https://issues.apache.org/jira/browse/LUCENE-2169" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/LUCENE-2169</a><br>> Project: Lucene - Java
<br>> Issue Type: Improvement
<br>> Components: Analysis
<br>> Affects Versions: 3.1
<br>> Reporter: Simon Willnauer
<br>> Assignee: Uwe Schindler
<br>> Fix For: 3.1
<br>>
<br>> Attachments: LUCENE-2169.patch, LUCENE-2169.patch, LUCENE-2169.patch, LUCENE-2169.patch
<br>>
<br>>
<br>> the copy method should use the entries array itself to copy the set internally instead of iterating over all values. this would speedup copying even small set
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26908783&i=0" target="_top" rel="nofollow">java-dev-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26908783&i=1" target="_top" rel="nofollow">java-dev-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/Lucene---Java-Developer-f46.html" embed="fixTarget[46]" target="_top" >Lucene - Java Developer</a></p>
tag:old.nabble.com,2006:post-26908770
Spatial Solr (JTeam)
2009-12-23T15:25:23Z
2009-12-23T15:25:23Z
Thomas Rabaix-2
Hello,
<br><br>I would like to set up the spatial solr plugin from
<br><a href="http://www.jteam.nl/news/spatialsolr" target="_top" rel="nofollow">http://www.jteam.nl/news/spatialsolr</a> on solr 1.4. However I am getting a
<br>error message when solr start.
<br><br>SEVERE: java.lang.NoClassDefFoundError: org/apache/solr/search/QParserPlugin
<br><br>I guess nl.jteam.search.solrext.spatial.SpatialTierQueryParserPlugin
<br>extends QParserPlugin. I have checked into the solr.war file (the one
<br>provided by solr download webpage) and the class is present.
<br><br>Do you know if the current version "SSP version 1.0-RC3" is compatible with
<br>solr 1.4 ?
<br><br>Thanks
<br><br>--
<br>Thomas Rabaix
<br><p>From forum: <a href="http://old.nabble.com/Solr---User-f14480.html" embed="fixTarget[14480]" target="_top" >Solr - User</a></p>
tag:old.nabble.com,2006:post-26908702
Re: Rename JIRA category from Matrix to Math
2009-12-23T15:18:36Z
2009-12-23T15:18:36Z
srowen
Done
<br><br>On Wed, Dec 23, 2009 at 9:56 PM, Benson Margulies <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26908702&i=0" target="_top" rel="nofollow">bimargulies@...</a>> wrote:
<br>> ?
<br>>
<br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26908445
[jira] Commented: (SOLR-236) Field collapsing
2009-12-23T14:43:29Z
2009-12-23T14:43:29Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794252#action_12794252" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794252#action_12794252</a> ]
<br><br>Uri Boness commented on SOLR-236:
<br>---------------------------------
<br><br>{quote}If we are returning a number of documents (as opposed to a number of groups) to the user, how do they avoid splitting on a page in the middle of the group?{quote}
<br><br>As far as I know (Martijn, correct me if I'm wrong), Martijn's patch returns the number of groups *and* documents, where each group is actually represented as a document. So in that sense, the total count applies to the result set as is (groups count as documents) and therefore pagination just works.
<br><br>{quote}The only thing this algorithm can't do (related to pagination) is give the total number of documents after collapsing (and hence can't calculate the exact number of pages). This can be fine in many circumstances as long as the gui handles it (people don't seem to mind google doing it... I just tried it. Google didn't show the result count right unless displaying the last page).{quote}
<br><br>First of all, I must admit that I never noticed that in Google, so I guess you're right :-). But when you think about it, with Google, how many time do you get a low hit count that only fits in 2-3 pages? Well, I hardly ever get it, and when I do I don't even bother to check the result I just try to improve my search. With Solr, a lot of times its different, specially when all these discovery features and faceting are so often used to narrow the search extensively... I'm not saying not having a perfect pagination mechanism is a problem... not at all, I'm just saying that it *might* be an issue for specific use cases or specific domains.... but that's just an assumption (or a gut feeling) :-)
<br><div class='shrinkable-quote'><br>> Field collapsing
<br>> ----------------
<br>>
<br>> Key: SOLR-236
<br>> URL: <a href="https://issues.apache.org/jira/browse/SOLR-236" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/SOLR-236</a><br>> Project: Solr
<br>> Issue Type: New Feature
<br>> Components: search
<br>> Affects Versions: 1.3
<br>> Reporter: Emmanuel Keller
<br>> Assignee: Shalin Shekhar Mangar
<br>> Fix For: 1.5
<br>>
<br>> Attachments: collapsing-patch-to-1.3.0-dieter.patch, collapsing-patch-to-1.3.0-ivan.patch, collapsing-patch-to-1.3.0-ivan_2.patch, collapsing-patch-to-1.3.0-ivan_3.patch, field-collapse-3.patch, field-collapse-4-with-solrj.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, field-collapse-solr-236-2.patch, field-collapse-solr-236.patch, field-collapsing-extended-592129.patch, field_collapsing_1.1.0.patch, field_collapsing_1.3.patch, field_collapsing_dsteigerwald.diff, field_collapsing_dsteigerwald.diff, field_collapsing_dsteigerwald.diff, quasidistributed.additional.patch, SOLR-236-FieldCollapsing.patch, SOLR-236-FieldCollapsing.patch, SOLR-236-FieldCollapsing.patch, SOLR-236.patch, SOLR-236.patch, SOLR-236.patch, SOLR-236.patch, solr-236.patch, SOLR-236_collapsing.patch, SOLR-236_collapsing.patch
<br>>
<br>>
<br>> This patch include a new feature called "Field collapsing".
<br>> "Used in order to collapse a group of results with similar value for a given field to a single entry in the result set. Site collapsing is a special case of this, where all results for a given web site is collapsed into one or two entries in the result set, typically with an associated "more documents from this site" link. See also Duplicate detection."
<br>> <a href="http://www.fastsearch.com/glossary.aspx?m=48&amid=299" target="_top" rel="nofollow">http://www.fastsearch.com/glossary.aspx?m=48&amid=299</a><br>> The implementation add 3 new query parameters (SolrParams):
<br>> "collapse.field" to choose the field used to group results
<br>> "collapse.type" normal (default value) or adjacent
<br>> "collapse.max" to select how many continuous results are allowed before collapsing
<br>> TODO (in progress):
<br>> - More documentation (on source code)
<br>> - Test cases
<br>> Two patches:
<br>> - "field_collapsing.patch" for current development version
<br>> - "field_collapsing_1.1.0.patch" for Solr-1.1.0
<br>> P.S.: Feedback and misspelling correction are welcome ;-)
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/Solr---Dev-f14481.html" embed="fixTarget[14481]" target="_top" >Solr - Dev</a></p>
tag:old.nabble.com,2006:post-26908367
[jira] Commented: (SOLR-1298) FunctionQuery results as pseudo-fields
2009-12-23T14:33:29Z
2009-12-23T14:33:29Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/jira/browse/SOLR-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794250#action_12794250" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/SOLR-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794250#action_12794250</a> ]
<br><br>Uri Boness commented on SOLR-1298:
<br>----------------------------------
<br><br>{quote}I think they should be inline, as they are just values associated with a document. I think putting it in some other list is sticking too literally to what Lucene calls a field, which I don't think Solr has to do that. One could easily imagine a Solr component that brought in a database or other storage repository for supplementary fields and it should all be seamless to the client.{quote}
<br><br>I definitely agree that one shouldn't see a field in Solr as a field in Lucene. That said, I think do have a tendency to see a field in Solr as somehow bound to the Solr schema.
<br><br>One thing to notice is that eventually we end up with the same discussion regarding this feature in the context of different issues, let it be highlighting or field collapsing. In some cases it feel just "right" to return the data as a field in a document, in other places it feels "right" to have as something else. It is true that when you interact with solr directly (specially if you do it manually) you certainly know what queries you send, what functions you request and what you should expect in the result. But from experience, a lot of times you try to automate things a bit and creating a well structured and descriptive protocols is the safe way to enable that.
<br><br>{quote}I don't want to have to go look it up in some other list while I am iterating over my results when all the other values I'm displaying/using are right there associated with the document.{quote}
<br><br>Having a sub-section under each documents still associates it with the document. The way I see it, It's like OOP... you can have a Person class that holds all the information of the person it it as primitive fields, or you can group related data, like address info, int a separate Address class.
<br><br>{quote}That being said, it could be useful to add an attribute that indicates it is a generated name{quote}
<br><br>That's one way to group fields together, but if you're already doing that, then why not go all the way? If you need to distinguish between generated and non-generated names, why not make it simpler and just separate the two in a different list? (To continue the analogies line I started above :-)) it's like XML, you can have a single level hierarchy were each element defines attributes to relate it to other elements, but a more suitable solution would just be to group all related elements under one parent element.
<br><br>{quote}I'd even argue that highlighter results should be inline, too, but that is a different issue and a bigger can of worms since it has a well used API already.{quote}
<br>In some cases it might be (well it just is) more appropriate to have the highlighting inlined. In other cases it might not be possible, specially with some of the latest requests to have highlighting functionality available for arbitrary text loaded from anywhere (which I believe will lead for a highlighting component/requestHandler that will be independent of the query component).
<br><br>{quote}Not saying this is right or wrong, but I think it would be useful to document here the rationale about why not to do it. Is it just b/c that method is expected to do, more or less, what the Lucene IndexSearcher does?{quote}
<br>I guess so... I guess SolrIndexSearcher is in fact a Lucene IndexSearcher which is the source for this association. In some ways I think it's also relates a bit to the response structure (not directly though, but conceptually)... if the IndexSearcher represents Lucene and the document contains fields coming from other sources as well, perhaps this functionality of gathering all these fields (/metadata ;-)) should be done in a higher level where SolrIndexSearcher just serves as on "field source". The main reason why Chris's patch puts this functionality in the doc() method of the SolrIndexSearcher is simply because it's the easiest and the simplest solution right now... and I don't thing there's nothing wrong with that... simple is good! Even with this solution as it is, the "field sources" are still abstracted away in the form of a "FieldValues" or "DocumentMutator", so architecture-wise I don't see leaving it as is will compromise anything.
<br><div class='shrinkable-quote'><br>> FunctionQuery results as pseudo-fields
<br>> --------------------------------------
<br>>
<br>> Key: SOLR-1298
<br>> URL: <a href="https://issues.apache.org/jira/browse/SOLR-1298" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/SOLR-1298</a><br>> Project: Solr
<br>> Issue Type: New Feature
<br>> Reporter: Grant Ingersoll
<br>> Assignee: Grant Ingersoll
<br>> Priority: Minor
<br>> Fix For: 1.5
<br>>
<br>> Attachments: SOLR-1298-FieldValues.patch, SOLR-1298.patch
<br>>
<br>>
<br>> It would be helpful if the results of FunctionQueries could be added as fields to a document.
<br>> Couple of options here:
<br>> 1. Run FunctionQuery as part of relevance score and add that piece to the document
<br>> 2. Run the function (not really a query) during Document/Field retrieval
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/Solr---Dev-f14481.html" embed="fixTarget[14481]" target="_top" >Solr - Dev</a></p>
tag:old.nabble.com,2006:post-26908289
Re: [math] found an apparent bug in Colt, now what?
2009-12-23T14:25:10Z
2009-12-23T14:25:10Z
Ted Dunning
Not entirely synthetic.
<br><br>We deprecated everything because we didn't entirely trust it. You just
<br>validated that suspicion.
<br><br>On Wed, Dec 23, 2009 at 1:56 PM, Benson Margulies <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26908289&i=0" target="_top" rel="nofollow">bimargulies@...</a>>wrote:
<br><br>> OK, in spite of the fact that one of those strikes is synthetic (ALL
<br>> of Colt was checked in deprecated), I've expunged it.
<br>>
<br><br><br><br>--
<br>Ted Dunning, CTO
<br>DeepDyve
<br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907978
Rename JIRA category from Matrix to Math
2009-12-23T13:56:58Z
2009-12-23T13:56:58Z
bimargulies
?
<br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907961
Re: [math] found an apparent bug in Colt, now what?
2009-12-23T13:56:29Z
2009-12-23T13:56:29Z
bimargulies
OK, in spite of the fact that one of those strikes is synthetic (ALL
<br>of Colt was checked in deprecated), I've expunged it.
<br><br>My latest patch, btw, has my swat at unit tests for the Sorting class.
<br><br>On Wed, Dec 23, 2009 at 4:46 PM, Jake Mannix <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907961&i=0" target="_top" rel="nofollow">jake.mannix@...</a>> wrote:
<div class='shrinkable-quote'><br>> Hmm. Function not used, deprecated, and broken. 3 strikes and it's out:
<br>> delete!
<br>>
<br>> On Wed, Dec 23, 2009 at 1:29 PM, Benson Margulies <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907961&i=1" target="_top" rel="nofollow">bimargulies@...</a>>wrote:
<br>>
<br>>> The Sorting class has an function called mergeSortInPlace. What it
<br>>> does not do is sort correctly. I am not sure what it is trying to do.
<br>>>
<br>>> I could:
<br>>>
<br>>> 1) Delete it. No other colt code calls it.
<br>>> 2) Mark it individually deprecated and move on, @Ignoring the test case.
<br>>> 3) Ask one of you folks to look at the code and see if it's worth
<br>>> bothering with.
<br>>>
<br>>
<br></div><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907906
[jira] Updated: (MAHOUT-229) Clean up and templatize the primitive list containers
2009-12-23T13:52:29Z
2009-12-23T13:52:29Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/jira/browse/MAHOUT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ]
<br><br>Benson Margulies updated MAHOUT-229:
<br>------------------------------------
<br><br> Fix Version/s: 0.4
<br> Status: Patch Available (was: Open)
<br><div class='shrinkable-quote'><br>> Clean up and templatize the primitive list containers
<br>> -----------------------------------------------------
<br>>
<br>> Key: MAHOUT-229
<br>> URL: <a href="https://issues.apache.org/jira/browse/MAHOUT-229" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-229</a><br>> Project: Mahout
<br>> Issue Type: Improvement
<br>> Components: Matrix
<br>> Affects Versions: 0.4
<br>> Reporter: Benson Margulies
<br>> Fix For: 0.4
<br>>
<br>> Attachments: array_list_patch.diff
<br>>
<br>>
<br>> Clean up the code in org.apache.mahout.math.list, including some testing and cleanup of some things that it calls.
<br>> This includes:
<br>> 1) More features in the Velocity code generator, including code to avoid generating a shadow of a checked-in file, and code to allow explicit suppression of individual outputs. Also an extra macro or two to make the template neater in some cases.
<br>> 2) The stack of code from AbstractList to AbstractXxxList to XxxArrayList generated with templates. AbstractCollection eliminated. ObjectArrayList preserved for now until the maps can be weaned from it.
<br>> 3) Removed 2 broken functions from the Sorting class.
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907907
[jira] Updated: (MAHOUT-229) Clean up and templatize the primitive list containers
2009-12-23T13:52:29Z
2009-12-23T13:52:29Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/jira/browse/MAHOUT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ]
<br><br>Benson Margulies updated MAHOUT-229:
<br>------------------------------------
<br><br> Attachment: array_list_patch.diff
<br><br>Lots of changes.
<br><div class='shrinkable-quote'><br>> Clean up and templatize the primitive list containers
<br>> -----------------------------------------------------
<br>>
<br>> Key: MAHOUT-229
<br>> URL: <a href="https://issues.apache.org/jira/browse/MAHOUT-229" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-229</a><br>> Project: Mahout
<br>> Issue Type: Improvement
<br>> Components: Matrix
<br>> Affects Versions: 0.4
<br>> Reporter: Benson Margulies
<br>> Fix For: 0.4
<br>>
<br>> Attachments: array_list_patch.diff
<br>>
<br>>
<br>> Clean up the code in org.apache.mahout.math.list, including some testing and cleanup of some things that it calls.
<br>> This includes:
<br>> 1) More features in the Velocity code generator, including code to avoid generating a shadow of a checked-in file, and code to allow explicit suppression of individual outputs. Also an extra macro or two to make the template neater in some cases.
<br>> 2) The stack of code from AbstractList to AbstractXxxList to XxxArrayList generated with templates. AbstractCollection eliminated. ObjectArrayList preserved for now until the maps can be weaned from it.
<br>> 3) Removed 2 broken functions from the Sorting class.
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907887
[jira] Created: (MAHOUT-229) Clean up and templatize the primitive list containers
2009-12-23T13:50:29Z
2009-12-23T13:50:29Z
JIRA jira@apache.org
Clean up and templatize the primitive list containers
<br>-----------------------------------------------------
<br><br> Key: MAHOUT-229
<br> URL: <a href="https://issues.apache.org/jira/browse/MAHOUT-229" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-229</a><br> Project: Mahout
<br> Issue Type: Improvement
<br> Components: Matrix
<br> Affects Versions: 0.4
<br> Reporter: Benson Margulies
<br><br><br>Clean up the code in org.apache.mahout.math.list, including some testing and cleanup of some things that it calls.
<br><br>This includes:
<br><br>1) More features in the Velocity code generator, including code to avoid generating a shadow of a checked-in file, and code to allow explicit suppression of individual outputs. Also an extra macro or two to make the template neater in some cases.
<br><br>2) The stack of code from AbstractList to AbstractXxxList to XxxArrayList generated with templates. AbstractCollection eliminated. ObjectArrayList preserved for now until the maps can be weaned from it.
<br><br>3) Removed 2 broken functions from the Sorting class.
<br><br><br><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907874
[jira] Commented: (MAHOUT-228) Need sequential logistic regression implementation using SGD techniques
2009-12-23T13:48:29Z
2009-12-23T13:48:29Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794230#action_12794230" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794230#action_12794230</a> ]
<br><br>Ted Dunning commented on MAHOUT-228:
<br>------------------------------------
<br><br><br>This implementation is purely logistic regression. Changing to other supervised learning algorithms shouldn't be difficult and I have made the regularization pluggable, but I would as soon get this working as is before adding too much generality. In particular, I have strongly used the presumption that I can do sparse updates and lazy regularization. I don't know how much that applies to other problems.
<br><div class='shrinkable-quote'><br>> Need sequential logistic regression implementation using SGD techniques
<br>> -----------------------------------------------------------------------
<br>>
<br>> Key: MAHOUT-228
<br>> URL: <a href="https://issues.apache.org/jira/browse/MAHOUT-228" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228</a><br>> Project: Mahout
<br>> Issue Type: New Feature
<br>> Components: Classification
<br>> Reporter: Ted Dunning
<br>> Fix For: 0.3
<br>>
<br>> Attachments: MAHOUT-228-1.patch
<br>>
<br>>
<br>> Stochastic gradient descent (SGD) is often fast enough for highly scalable learning (see Vowpal Wabbit, <a href="http://hunch.net/~vw/" target="_top" rel="nofollow">http://hunch.net/~vw/</a>).
<br>> I often need to have a logistic regression in Java as well, so that is a reasonable place to start.
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907844
Re: [math] found an apparent bug in Colt, now what?
2009-12-23T13:46:02Z
2009-12-23T13:46:02Z
Jake Mannix
Hmm. Function not used, deprecated, and broken. 3 strikes and it's out:
<br>delete!
<br><br>On Wed, Dec 23, 2009 at 1:29 PM, Benson Margulies <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907844&i=0" target="_top" rel="nofollow">bimargulies@...</a>>wrote:
<br><div class='shrinkable-quote'><br>> The Sorting class has an function called mergeSortInPlace. What it
<br>> does not do is sort correctly. I am not sure what it is trying to do.
<br>>
<br>> I could:
<br>>
<br>> 1) Delete it. No other colt code calls it.
<br>> 2) Mark it individually deprecated and move on, @Ignoring the test case.
<br>> 3) Ask one of you folks to look at the code and see if it's worth
<br>> bothering with.
<br>>
<br></div><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907800
Re: [jira] Updated: (MAHOUT-228) Need sequential logistic regression implementation using SGD techniques
2009-12-23T13:41:03Z
2009-12-23T13:41:03Z
Ted Dunning
It's there.
<br><br>On Wed, Dec 23, 2009 at 1:38 PM, Ted Dunning <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907800&i=0" target="_top" rel="nofollow">ted.dunning@...</a>> wrote:
<br><br>>
<br>> I always forget that marking patch available doesn't actually make the
<br>> patch available.
<br>>
<br>> Patch will be there very shortly.
<br>>
<br>>
<br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907789
[jira] Updated: (MAHOUT-228) Need sequential logistic regression implementation using SGD techniques
2009-12-23T13:40:29Z
2009-12-23T13:40:29Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ]
<br><br>Ted Dunning updated MAHOUT-228:
<br>-------------------------------
<br><br> Attachment: MAHOUT-228-1.patch
<br><br>Here is the actual patch file.
<br><div class='shrinkable-quote'><br>> Need sequential logistic regression implementation using SGD techniques
<br>> -----------------------------------------------------------------------
<br>>
<br>> Key: MAHOUT-228
<br>> URL: <a href="https://issues.apache.org/jira/browse/MAHOUT-228" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228</a><br>> Project: Mahout
<br>> Issue Type: New Feature
<br>> Components: Classification
<br>> Reporter: Ted Dunning
<br>> Fix For: 0.3
<br>>
<br>> Attachments: MAHOUT-228-1.patch
<br>>
<br>>
<br>> Stochastic gradient descent (SGD) is often fast enough for highly scalable learning (see Vowpal Wabbit, <a href="http://hunch.net/~vw/" target="_top" rel="nofollow">http://hunch.net/~vw/</a>).
<br>> I often need to have a logistic regression in Java as well, so that is a reasonable place to start.
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907790
Re: [math] found an apparent bug in Colt, now what?
2009-12-23T13:40:15Z
2009-12-23T13:40:15Z
Ted Dunning
Delete it. (echo ... echo)
<br><br>On Wed, Dec 23, 2009 at 1:35 PM, Sean Owen <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907790&i=0" target="_top" rel="nofollow">srowen@...</a>> wrote:
<br><div class='shrinkable-quote'><br>> Delete it
<br>>
<br>> On Wed, Dec 23, 2009 at 9:29 PM, Benson Margulies <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907790&i=1" target="_top" rel="nofollow">bimargulies@...</a>>
<br>> wrote:
<br>> > The Sorting class has an function called mergeSortInPlace. What it
<br>> > does not do is sort correctly. I am not sure what it is trying to do.
<br>> >
<br>> > I could:
<br>> >
<br>> > 1) Delete it. No other colt code calls it.
<br>> > 2) Mark it individually deprecated and move on, @Ignoring the test case.
<br>> > 3) Ask one of you folks to look at the code and see if it's worth
<br>> > bothering with.
<br>> >
<br>>
</div><br><br><br>--
<br>Ted Dunning, CTO
<br>DeepDyve
<br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907777
Re: [jira] Updated: (MAHOUT-228) Need sequential logistic regression implementation using SGD techniques
2009-12-23T13:38:31Z
2009-12-23T13:38:31Z
Ted Dunning
I always forget that marking patch available doesn't actually make the patch
<br>available.
<br><br>Patch will be there very shortly.
<br><br>On Wed, Dec 23, 2009 at 1:20 PM, Jake Mannix <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907777&i=0" target="_top" rel="nofollow">jake.mannix@...</a>> wrote:
<br><div class='shrinkable-quote'><br>> Wait, I thought there was a patch, is there no code on this yet? The JIRA
<br>> ticket
<br>> says "patch available", but there's no files attached?
<br>>
<br>> -jake
<br>>
<br>> On Wed, Dec 23, 2009 at 1:15 PM, Jake Mannix <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907777&i=1" target="_top" rel="nofollow">jake.mannix@...</a>>
<br>> wrote:
<br>>
<br>> > Hey Ted,
<br>> >
<br>> > I'll try out the patch, but I doubt it duplicates any of the stuff I've
<br>> > got coming in - I've
<br>> > been meaning to put together an SGD impl, but while ideologically it
<br>> > overlaps with some
<br>> > of my decomposition stuff (and the current in-memory SVD which is in
<br>> Taste
<br>> > is actually
<br>> > of the SGD variety, so there may be some overlap with that) but any
<br>> > scalable impl of
<br>> > that would be awesome.
<br>> >
<br>> > But this patch is for SGD for logistic regression, right? How
<br>> > customizable is it for
<br>> > solving different plugged in optimization functions? I guess I could
<br>> just
<br>> > try it out and
<br>> > see, eh?
<br>> >
<br>> > -jake
<br>> >
<br>> >
<br>> > On Wed, Dec 23, 2009 at 12:52 PM, Ted Dunning <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907777&i=2" target="_top" rel="nofollow">ted.dunning@...</a>
<br>> >wrote:
<br>> >
<br>> >> Jake,
<br>> >>
<br>> >> I would appreciate your comments on this, especially in light of any
<br>> >> duplication.
<br>> >>
<br>> >> David,
<br>> >>
<br>> >> If you have any time, your comments are always very welcome as well.
<br>> >>
<br>> >> On Wed, Dec 23, 2009 at 12:50 PM, Ted Dunning (JIRA) <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907777&i=3" target="_top" rel="nofollow">jira@...</a>
<br>> >> >wrote:
<br>> >>
<br>> >> >
<br>> >> > [
<br>> >> >
<br>> >>
<br>> <a href="https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a><br>> >> ]
<br>> >> >
<br>> >> > Ted Dunning updated MAHOUT-228:
<br>> >> > -------------------------------
<br>> >> >
<br>> >> > Fix Version/s: 0.3
<br>> >> > Status: Patch Available (was: Open)
<br>> >> >
<br>> >> > Here is an early implementation. The learning has been implemented,
<br>> but
<br>> >> > not tested. Most other aspects are reasonably well tested.
<br>> >> >
<br>> >> > > Need sequential logistic regression implementation using SGD
<br>> >> techniques
<br>> >> > >
<br>> >> -----------------------------------------------------------------------
<br>> >> > >
<br>> >> > > Key: MAHOUT-228
<br>> >> > > URL:
<br>> <a href="https://issues.apache.org/jira/browse/MAHOUT-228" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228</a><br>> >> > > Project: Mahout
<br>> >> > > Issue Type: New Feature
<br>> >> > > Components: Classification
<br>> >> > > Reporter: Ted Dunning
<br>> >> > > Fix For: 0.3
<br>> >> > >
<br>> >> > >
<br>> >> > > Stochastic gradient descent (SGD) is often fast enough for highly
<br>> >> > scalable learning (see Vowpal Wabbit, <a href="http://hunch.net/~vw/" target="_top" rel="nofollow">http://hunch.net/~vw/</a><<a href="http://hunch.net/%7Evw/" target="_top" rel="nofollow">http://hunch.net/%7Evw/</a>>
<br>> <
<br>> >> <a href="http://hunch.net/%7Evw/" target="_top" rel="nofollow">http://hunch.net/%7Evw/</a>>
<br>> >> > ).
<br>> >> > > I often need to have a logistic regression in Java as well, so that
<br>> is
<br>> >> a
<br>> >> > reasonable place to start.
<br>> >> >
<br>> >> > --
<br>> >> > This message is automatically generated by JIRA.
<br>> >> > -
<br>> >> > You can reply to this email to add a comment to the issue online.
<br>> >> >
<br>> >> >
<br>> >>
<br>> >>
<br>> >> --
<br>> >> Ted Dunning, CTO
<br>> >> DeepDyve
<br>> >>
<br>> >
<br>> >
<br>>
</div><br><br><br>--
<br>Ted Dunning, CTO
<br>DeepDyve
<br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907735
Re: [math] found an apparent bug in Colt, now what?
2009-12-23T13:35:41Z
2009-12-23T13:35:41Z
srowen
Delete it
<br><br>On Wed, Dec 23, 2009 at 9:29 PM, Benson Margulies <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907735&i=0" target="_top" rel="nofollow">bimargulies@...</a>> wrote:
<div class='shrinkable-quote'><br>> The Sorting class has an function called mergeSortInPlace. What it
<br>> does not do is sort correctly. I am not sure what it is trying to do.
<br>>
<br>> I could:
<br>>
<br>> 1) Delete it. No other colt code calls it.
<br>> 2) Mark it individually deprecated and move on, @Ignoring the test case.
<br>> 3) Ask one of you folks to look at the code and see if it's worth
<br>> bothering with.
<br>>
<br></div><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907711
Re: Field Collapsing - disable cache
2009-12-23T13:33:16Z
2009-12-23T13:33:16Z
Martijn v Groningen
How have you configured field collapsing?
<br>I have field collapsing configured without caching like this:
<br><searchComponent name="collapse"
<br>class="org.apache.solr.handler.component.CollapseComponent" />
<br><br>and with caching like this:
<br><searchComponent name="collapse"
<br>class="org.apache.solr.handler.component.CollapseComponent">
<br><br> <fieldCollapseCache
<br> class="solr.FastLRUCache"
<br> size="512"
<br> initialSize="512"
<br> autowarmCount="128"/>
<br><br> </searchComponent>
<br><br>In both situations I don't get NPE. Also the line (in the patch) where
<br>the exceptions occurs seems unlikely for a NPE.
<br>if (fieldCollapseCache != null) {
<br> fieldCollapseCache.put(currentCacheKey, new CacheValue(result,
<br>collectors, collapseContext)); // line 276
<br>}
<br><br>Does the exception occur immediately after the first search?
<br><br>Martijn
<br><br>2009/12/23 <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907711&i=0" target="_top" rel="nofollow">rob@...</a>>:
<div class='shrinkable-quote'><br>>
<br>> Still seeing the same error when trying to comment out the fieldCollapsing block, or even just the fieldCollapseCache block inside it to disable the cache.
<br>>
<br>> fresh trunk and latest patch.
<br>>
<br>>
<br>>
<br>> message null java.lang.NullPointerException at org.apache.solr.search.fieldcollapse.AbstractDocumentCollapser.createDocumentCollapseResult(AbstractDocumentCollapser.java:276) at org.apache.solr.search.fieldcollapse.AbstractDocumentCollapser.executeCollapse(AbstractDocumentCollapser.java:249) at org.apache.solr.search.fieldcollapse.AbstractDocumentCollapser.collapse(AbstractDocumentCollapser.java:172) at org.apache.solr.handler.component.CollapseComponent.doProcess(CollapseComponent.java:173) at org.apache.solr.handler.component.CollapseComponent.process(CollapseComponent.java:127) at org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:195) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:131) at org.apache.solr.core.SolrCore.execute(SolrCore.java:1316) at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:336) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:239) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) at java.lang.Thread.run(Thread.java:636)
<br>>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>> On Wed 23/12/09 13:26 , <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907711&i=1" target="_top" rel="nofollow">rob@...</a> wrote:
<br>>
<br>>> Thanks, that latest update to the patch works fine now.
<br>>> On Wed 23/12/09 13:13 , Martijn v Groningen wrote:
<br>>> > Latest SOLR-236.patch is for the trunk, if have updated the latest
<br>>> > patch so it should patch now without conflicts. If I remember
<br>>> > correctly the latest field-collapse-5.patch should work for 1.4,
<br>>> but
<br>>> > it doesn't for the trunk.
<br>>> > 2009/12/23 :
<br>>> > >
<br>>> > > Sorry, that was when trying to patch the 1.4 branch
<br>>> > >
<br>>> > > attempting to patch the trunk gives...
<br>>> > >
<br>>> > > patching file src/test/test-files/fieldcollapse/testResponse.xml
<br>>> > > patching file
<br>>> > src/test/org/apache/solr/BaseDistributedSearchTestCase.java
<br>>> > > Hunk #2 FAILED at 502.
<br>>> > > 1 out of 2 hunks FAILED -- saving rejects to file
<br>>> > src/test/org/apache/solr/BaseDistributedSearchTestCase.java.rej
<br>>> > > patching file
<br>>> >
<br>>> src/test/org/apache/solr/search/fieldcollapse/FieldCollapsingIntegrationTes
<br>>> > t.java>
<br>>> > >
<br>>> > > btw, when is trunk actually updated?
<br>>> > >
<br>>> > >
<br>>> > >
<br>>> > >
<br>>> > >
<br>>> > > On Wed 23/12/09 11:53 , wrote:
<br>>> > >
<br>>> > >> I'm currently trying to patch aginst trunk, using
<br>>> SOLR-236.patch
<br>>> > >> from 18/12/2009 but getting the following error...
<br>>> > >> [ solr]$ patch -p0 < SOLR-236.patch
<br>>> > >> patching file
<br>>> > >> src/test/test-files/solr/conf/solrconfig-fieldcollapse.xml
<br>>> > >> patching file
<br>>> > src/test/test-files/solr/conf/schema-fieldcollapse.xml
<br>>> > >> patching file src/test/test-files/solr/conf/solrconfig.xml
<br>>> > >> patching file
<br>>> src/test/test-files/fieldcollapse/testResponse.xml
<br>>> > >> can't find file to patch at input line 787
<br>>> > >> Perhaps you used the wrong -p or --strip option?
<br>>> > >> The text leading up to this was:
<br>>> > >> --------------------------
<br>>> > >> |
<br>>> > >> |Property changes on:
<br>>> > >> src/test/test-files/fieldcollapse/testResponse.xml
<br>>> > >>
<br>>> >
<br>>> |___________________________________________________________________
<br>>> > >> |Added: svn:keywords
<br>>> > >> | + Date Author Id Revision HeadURL
<br>>> > >> |Added: svn:eol-style
<br>>> > >> | + native
<br>>> > >> |
<br>>> > >> |Index:
<br>>> > src/test/org/apache/solr/BaseDistributedSearchTestCase.java
<br>>> > >>
<br>>> >
<br>>> |===================================================================
<br>>> > >> |---
<br>>> src/test/org/apache/solr/BaseDistributedSearchTestCase.java
<br>>> > >> (revision 891214)
<br>>> > >> |+++
<br>>> src/test/org/apache/solr/BaseDistributedSearchTestCase.java
<br>>> > >> (working copy)
<br>>> > >> --------------------------
<br>>> > >> File to patch:
<br>>> > >> any suggestions, or should i checkout the 1.4 branch instead?
<br>>> > >> can't remember what i did last time to get
<br>>> field-collapse-5.patch
<br>>> > >> working successfully.
<br>>> > >> On Tue 22/12/09 22:43 , Lance Norskog wrote:
<br>>> > >> > To avoid this possible bug, you could change the cache to
<br>>> only
<br>>> > >> have a
<br>>> > >> > few entries.
<br>>> > >> > On Tue, Dec 22, 2009 at 6:34 AM, Martijn v Groningen
<br>>> > >> > wrote:
<br>>> > >> > > In the latest patch some changes where made on the
<br>>> > configuration
<br>>> > >> > side,
<br>>> > >> > > but if you add the CollapseComponent to the conf no field
<br>>> > >> collapse
<br>>> > >> > > cache should be enabled. If not let me know.
<br>>> > >> > >
<br>>> > >> > > Martijn
<br>>> > >> > >
<br>>> > >> > > 2009/12/22 :
<br>>> > >> > >>
<br>>> > >> > >>
<br>>> > >> > >>
<br>>> > >> > >>
<br>>> > >> > >>
<br>>> > >> > >> On Tue 22/12/09 12:28 , Martijn v Groningen wrote:
<br>>> > >> > >>
<br>>> > >> > >>> Hi Rob,
<br>>> > >> > >>> What patch are you actually using from SOLR-236?
<br>>> > >> > >>> Martijn
<br>>> > >> > >>> 2009/12/22 :
<br>>> > >> > >>> > I've tried both, the whole fieldCollapsing tag, and
<br>>> just
<br>>> > the
<br>>> > >> > >>> > fieldCollapseCache tag inside it.
<br>>> > >> > >>> > both cause error.
<br>>> > >> > >>> > I guess I can just set size, initialSize, and
<br>>> > >> > autowarmCount
<br>>> > >> > >>> to 0 ??
<br>>> > >> > >>> > On Tue 22/12/09 11:17 , Toby Cole wrote:Which elements
<br>>> > did
<br>>> > >> > you
<br>>> > >> > >>> > comment out? It could be the case that you need
<br>>> > >> > >>> > to get rid of the entire fieldCollapsing element, not
<br>>> > just
<br>>> > >> the
<br>>> > >> > >>> > fieldCollapsingCache element.
<br>>> > >> > >>> > (Disclaimer: I've not used field collapsing in anger
<br>>> > before
<br>>> > >> :)
<br>>> > >> > >>> > Toby.
<br>>> > >> > >>> >
<br>>> > >> > >>> > On 22 Dec 2009, at 11:09, wrote:
<br>>> > >> > >>> >
<br>>> > >> > >>> >> That's what I assumed, but I'm getting the following
<br>>> > error
<br>>> > >> > with
<br>>> > >> > >>> it
<br>>> > >> > >>> >> commented out....
<br>>> > >> > >>> >> MESSAGE null java.lang.NullPointerException at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >> .solr
<br>>> > >> > >>> >> .search
<br>>> > >> > >>> >> .fieldcollapse
<br>>> > >> > >>> >> .AbstractDocumentCollapser
<br>>> > >> > >>> >>
<br>>> > >> >
<br>>> > .createDocumentCollapseResult(AbstractDocumentCollapser.java:276)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >> .solr
<br>>> > >> > >>> >> .search
<br>>> > >> > >>> >> .fieldcollapse
<br>>> > >> > >>> >> .AbstractDocumentCollapser
<br>>> > >> > >>> >> .executeCollapse(AbstractDocumentCollapser.java:249)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >> .solr
<br>>> > >> > >>> >> .search
<br>>> > >> > >>> >> .fieldcollapse
<br>>> > >> > >>> >>
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .AbstractDocumentCollapser.collapse(AbstractDocumentCollapser.java:
<br>>> > >> > >>> >
<br>>> > >> > >>> >> 172)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >> .solr
<br>>> > >> > >>> >> .handler
<br>>> > >> > >>> >>
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > .component.CollapseComponent.doProcess(CollapseComponent.java:173)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >> .solr
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .handler.component.CollapseComponent.process(CollapseComponent.java:
<br>>> > >> > >>> >> 127)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >> .solr
<br>>> > >> > >>> >> .handler
<br>>> > >> > >>> >>
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > .component.SearchHandler.handleRequestBody(SearchHandler.java:195)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >> .solr
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:131)
<br>>> > >> > >>> >> at
<br>>> > >> org.apache.solr.core.SolrCore.execute(SolrCore.java:1316)
<br>>> > >> > at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:336)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:239)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >> .catalina
<br>>> > >> > >>> >> .core
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:
<br>>> > >> > >>> >
<br>>> > >> > >>> >> 215)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >> .catalina
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:
<br>>> > >> > >>> >
<br>>> > >> > >>> >> 210)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .catalina.core.StandardContextValve.invoke(StandardContextValve.java:
<br>>> > >> > >>> >
<br>>> > >> > >>> >> 172)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >>
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >>
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >>
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:
<br>>> > >> > >>> >
<br>>> > >> > >>> >> 108)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:
<br>>> > >> > >>> >> 151)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >>
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .apache.coyote.http11.Http11Processor.process(Http11Processor.java:
<br>>> > >> > >>> >
<br>>> > >> > >>> >> 870)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org.apache.coyote.http11.Http11BaseProtocol
<br>>> > >> > >>> >>
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> $Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:
<br>>> > >> > >>> >
<br>>> > >> > >>> >> 665)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:
<br>>> > >> > >>> >> 528)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org
<br>>> > >> > >>> >> .apache
<br>>> > >> > >>> >> .tomcat
<br>>> > >> > >>> >> .util
<br>>> > >> > >>> >> .net
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> .LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
<br>>> > >> > >>> >> at
<br>>> > >> > >>> >> org.apache.tomcat.util.threads.ThreadPool
<br>>> > >> > >>> >> $ControlRunnable.run(ThreadPool.java:685)
<br>>> > >> > >>> >> at java.lang.Thread.run(Thread.java:636)
<br>>> > >> > >>> >> On Tue 22/12/09 11:02 , Toby Cole wrote:If you take
<br>>> out
<br>>> > >> the
<br>>> > >> > >>> >> fieldCollapsing/fieldCollapseCache element in your
<br>>> > >> > >>> >> config the fieldcollapse component will not use a
<br>>> cache.
<br>>> > >> > >>> >> From
<br>>> > >> <a href="http://wiki.apache.org/solr/FieldCollapsing%2523line-63" target="_top" rel="nofollow">http://wiki.apache.org/solr/FieldCollapsing%2523line-63</a><br>>> > >> > [2]"
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> target="_blank"><a href="http://wiki.apache.org/solr/FieldCollapsing%23line-63" target="_top" rel="nofollow">http://wiki.apache.org/solr/FieldCollapsing%23line-63</a><br>>> > >> > >>> > [1]"
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> target="_blank"><a href="http://wiki.apache.org/solr/FieldCollapsing%23line-63" target="_top" rel="nofollow">http://wiki.apache.org/solr/FieldCollapsing%23line-63</a><br>>> > >> > >>> > [3]"
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> target="_blank"><a href="http://wiki.apache.org/solr/FieldCollapsing#line-63" target="_top" rel="nofollow">http://wiki.apache.org/solr/FieldCollapsing#line-63</a><br>>> > >> > >>> >> "If the field collapse cache is not configured then
<br>>> the
<br>>> > >> field
<br>>> > >> > >>> >> collapse logic will not be cached."
<br>>> > >> > >>> >>
<br>>> > >> > >>> >> Regards, Toby.
<br>>> > >> > >>> >>
<br>>> > >> > >>> >> On 22 Dec 2009, at 10:56, wrote:
<br>>> > >> > >>> >>
<br>>> > >> > >>> >>> my
<br>>> > >> > >>> >>> solconfig can be seen at
<br>>> > >> > >>> > <a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a> [4]"
<br>>> > >> > >>> >
<br>>> > target="_blank"><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>>> > >> > >>> >> [3]"
<br>>> > >> > target="_blank"><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>>> > >> > >>> > [5]"
<br>>> > >> > target="_blank"><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>>> > >> > >>> >>> [1]
<br>>> > >> > >>> >>> On Tue 22/12/09 10:51 , wrote:Is
<br>>> > >> > >>> >>> it possible to disable the field collapsing cache?
<br>>> I'm
<br>>> > >> > trying
<br>>> > >> > >>> to
<br>>> > >> > >>> >>> perform some speed tests, and have managed to comment
<br>>> > out
<br>>> > >> > the
<br>>> > >> > >>> >> filter,
<br>>> > >> > >>> >>> queryResult, and document caches successfully.
<br>>> > >> > >>> >>>
<br>>> > >> > >>> >>> on 1.5
<br>>> > >> > >>> >>> ...
<br>>> > >> > >>> >>> ...
<br>>> > >> > >>> >>> collapse
<br>>> > >> > >>> >>>
<br>>> > >> > >>> >>> facet
<br>>> > >> > >>> >>>
<br>>> > >> > >>> >>> tvComponent
<br>>> > >> > >>> >>> ...
<br>>> > >> > >>> >>> -------------------------
<br>>> > >> > >>> >>> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>>> [6]"
<br>>> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [5]"
<br>>> > >> > >>> >> target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [7]"
<br>>> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [2]"
<br>>> > >> > >>> >>> target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [8]"
<br>>> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [6]"
<br>>> > >> > >>> >> target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [9]"
<br>>> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>>> > >> > >>> >>> -------------------------
<br>>> > >> > >>> >>> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>>> [10]"
<br>>> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [7]"
<br>>> > >> > >>> >> target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a> [11]"
<br>>> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>>> > >> > >>> >>>
<br>>> > >> > >>> >>> Links:
<br>>> > >> > >>> >>> ------
<br>>> > >> > >>> >>> [1] <a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a> [12]"
<br>>> > >> > >>> >
<br>>> > target="_blank"><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>>> > >> > [8]"
<br>>> > >> > >>> >>
<br>>> > target="_blank"><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>>> > >> > [13]"
<br>>> > >> > >>> >
<br>>> > target="_blank"><a href="http://www.intelcompute.com/solrconfig.xml" target="_top" rel="nofollow">http://www.intelcompute.com/solrconfig.xml</a><br>>> > >> > >>> >>> [2]
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> <a href="http://mail.intelcompute.com/parse.php%253Fredirect%253D%2526lt%253Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%253Fredirect%253D%2526lt%253Ba</a><br>>> > >> > >>> > [14]"
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> target="_blank"><a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3</a><br>>> > >> > >>> Ba>> [9]"
<br>>> > >> > >>> >>
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> target="_blank"><a href="http://mail.intelcompute.com/parse.php%3Fredirect%3Dhttp://" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3Dhttp://</a><br>>> > >> > >>> blogs.semantico.com/discovery-blog/> [15]"
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=http://blog" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=http://blog</a><br>>> > >> > >>> s.semantico.com/discovery-blog/> [16]
<br>>> > >> > >>> >> -------------------------
<br>>> > >> > >>> >> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>>> [17]"
<br>>> > >> > >>> > target="_blank"><a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>>> > >> > >>> >>
<br>>> > >> > >>> >> Links:
<br>>> > >> > >>> >> ------
<br>>> > >> > >>> >> [1]
<br>>> > >> > <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>>> > >> > >>> > [18]"
<br>>> > >> > >>> >
<br>>> > >> >
<br>>> > target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>>> > >> > >>> [3]
<br>>> > >> > >>> >
<br>>> > >> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>>> > >> > >>> [19]"
<br>>> > >> > >>> >
<br>>> > >> >
<br>>> > target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>>> > >> > >>> [5]
<br>>> > >> > >>> >
<br>>> > >> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>>> > >> > >>> [20]"
<br>>> > >> > >>> >
<br>>> > >> >
<br>>> > target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>>> > >> > >>> [6]
<br>>> > >> > >>> >
<br>>> > >> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>>> > >> > >>> [21]"
<br>>> > >> > >>> >
<br>>> > >> >
<br>>> > target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>>> > >> > >>> [7]
<br>>> > >> > >>> >
<br>>> > >> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>>> > >> > >>> [22]"
<br>>> > >> > >>> >
<br>>> > >> >
<br>>> > target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>>> > >> > >>> [8]
<br>>> > >> > >>> >
<br>>> > >> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>>> > >> > >>> [23]"
<br>>> > >> > >>> >
<br>>> > >> >
<br>>> > target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>>> > >> > >>> [9]
<br>>> > >> > >>> >
<br>>> > >> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>>> > >> > >>> [24]"
<br>>> > >> > >>> >
<br>>> > >> >
<br>>> > target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>>> > >> > >>> [10]
<br>>> > >> > >>> >
<br>>> > >> <a href="http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php%3Fredirect%3D%26lt%3Ba</a><br>>> > >> > >>> [25]"
<br>>> > >> > >>> >
<br>>> > >> > >>>
<br>>> > >> >
<br>>> > >>
<br>>> >
<br>>> target="_blank"><a href="http://mail.intelcompute.com/parse.php?redirect=http://blog" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=http://blog</a><br>>> > >> > >>> s.semantico.com/discovery-blog/>
<br>>> -------------------------
<br>>> > >> > >>> > Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>>> > >> > >>> >
<br>>> > >> > >>> > Links:
<br>>> > >> > >>> > ------
<br>>> > >> > >>> > [2] <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>>> [3]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [4]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [5]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [6]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [7]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [8]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [9]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [10]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [11]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [12]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [13]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [14]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [15]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [16]
<br>>> > >> > >>> <a href="http://blogs.semantico.com/discovery-blog/" target="_top" rel="nofollow">http://blogs.semantico.com/discovery-blog/</a><br>>> > >> > >>> > [17] <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>>> > [18]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [19]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [20]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [21]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [22]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [23]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [24]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [25]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a> [27]
<br>>> > >> > >>> <a href="http://mail.intelcompute.com/parse.php?redirect=" target="_top" rel="nofollow">http://mail.intelcompute.com/parse.php?redirect=</a><br>>> > >> > >>> --
<br>>> > >> > >>> Met vriendelijke groet,
<br>>> > >> > >>> Martijn van Groningen
<br>>> > >> > >>>
<br>>> > >> > >>>
<br>>> > >> > >> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>>> > >> > >>
<br>>> > >> > >
<br>>> > >> > >
<br>>> > >> > >
<br>>> > >> > > --
<br>>> > >> > > Met vriendelijke groet,
<br>>> > >> > >
<br>>> > >> > > Martijn van Groningen
<br>>> > >> > >
<br>>> > >> > --
<br>>> > >> > Lance Norskog
<br>>> > >> >
<br>>> > >> >
<br>>> > >> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>>> > >>
<br>>> > >>
<br>>> > > Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>>> > >
<br>>> > --
<br>>> > Met vriendelijke groet,
<br>>> > Martijn van Groningen
<br>>> >
<br>>> >
<br>>> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>>>
<br>>>
<br>> Message sent via Atmail Open - <a href="http://atmail.org/" target="_top" rel="nofollow">http://atmail.org/</a><br>>
</div><br><br><br>--
<br>Met vriendelijke groet,
<br><br>Martijn van Groningen
<br><p>From forum: <a href="http://old.nabble.com/Solr---User-f14480.html" embed="fixTarget[14480]" target="_top" >Solr - User</a></p>
tag:old.nabble.com,2006:post-26907661
[math] found an apparent bug in Colt, now what?
2009-12-23T13:29:57Z
2009-12-23T13:29:57Z
bimargulies
The Sorting class has an function called mergeSortInPlace. What it
<br>does not do is sort correctly. I am not sure what it is trying to do.
<br><br>I could:
<br><br>1) Delete it. No other colt code calls it.
<br>2) Mark it individually deprecated and move on, @Ignoring the test case.
<br>3) Ask one of you folks to look at the code and see if it's worth
<br>bothering with.
<br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907567
Re: [jira] Updated: (MAHOUT-228) Need sequential logistic regression implementation using SGD techniques
2009-12-23T13:20:51Z
2009-12-23T13:20:51Z
Jake Mannix
Wait, I thought there was a patch, is there no code on this yet? The JIRA
<br>ticket
<br>says "patch available", but there's no files attached?
<br><br> -jake
<br><br>On Wed, Dec 23, 2009 at 1:15 PM, Jake Mannix <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907567&i=0" target="_top" rel="nofollow">jake.mannix@...</a>> wrote:
<br><div class='shrinkable-quote'><br>> Hey Ted,
<br>>
<br>> I'll try out the patch, but I doubt it duplicates any of the stuff I've
<br>> got coming in - I've
<br>> been meaning to put together an SGD impl, but while ideologically it
<br>> overlaps with some
<br>> of my decomposition stuff (and the current in-memory SVD which is in Taste
<br>> is actually
<br>> of the SGD variety, so there may be some overlap with that) but any
<br>> scalable impl of
<br>> that would be awesome.
<br>>
<br>> But this patch is for SGD for logistic regression, right? How
<br>> customizable is it for
<br>> solving different plugged in optimization functions? I guess I could just
<br>> try it out and
<br>> see, eh?
<br>>
<br>> -jake
<br>>
<br>>
<br>> On Wed, Dec 23, 2009 at 12:52 PM, Ted Dunning <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907567&i=1" target="_top" rel="nofollow">ted.dunning@...</a>>wrote:
<br>>
<br>>> Jake,
<br>>>
<br>>> I would appreciate your comments on this, especially in light of any
<br>>> duplication.
<br>>>
<br>>> David,
<br>>>
<br>>> If you have any time, your comments are always very welcome as well.
<br>>>
<br>>> On Wed, Dec 23, 2009 at 12:50 PM, Ted Dunning (JIRA) <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907567&i=2" target="_top" rel="nofollow">jira@...</a>
<br>>> >wrote:
<br>>>
<br>>> >
<br>>> > [
<br>>> >
<br>>> <a href="https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a><br>>> ]
<br>>> >
<br>>> > Ted Dunning updated MAHOUT-228:
<br>>> > -------------------------------
<br>>> >
<br>>> > Fix Version/s: 0.3
<br>>> > Status: Patch Available (was: Open)
<br>>> >
<br>>> > Here is an early implementation. The learning has been implemented, but
<br>>> > not tested. Most other aspects are reasonably well tested.
<br>>> >
<br>>> > > Need sequential logistic regression implementation using SGD
<br>>> techniques
<br>>> > >
<br>>> -----------------------------------------------------------------------
<br>>> > >
<br>>> > > Key: MAHOUT-228
<br>>> > > URL: <a href="https://issues.apache.org/jira/browse/MAHOUT-228" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228</a><br>>> > > Project: Mahout
<br>>> > > Issue Type: New Feature
<br>>> > > Components: Classification
<br>>> > > Reporter: Ted Dunning
<br>>> > > Fix For: 0.3
<br>>> > >
<br>>> > >
<br>>> > > Stochastic gradient descent (SGD) is often fast enough for highly
<br>>> > scalable learning (see Vowpal Wabbit, <a href="http://hunch.net/~vw/" target="_top" rel="nofollow">http://hunch.net/~vw/</a><
<br>>> <a href="http://hunch.net/%7Evw/" target="_top" rel="nofollow">http://hunch.net/%7Evw/</a>>
<br>>> > ).
<br>>> > > I often need to have a logistic regression in Java as well, so that is
<br>>> a
<br>>> > reasonable place to start.
<br>>> >
<br>>> > --
<br>>> > This message is automatically generated by JIRA.
<br>>> > -
<br>>> > You can reply to this email to add a comment to the issue online.
<br>>> >
<br>>> >
<br>>>
<br>>>
<br>>> --
<br>>> Ted Dunning, CTO
<br>>> DeepDyve
<br>>>
<br>>
<br>>
<br></div><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907504
Re: [jira] Updated: (MAHOUT-228) Need sequential logistic regression implementation using SGD techniques
2009-12-23T13:15:11Z
2009-12-23T13:15:11Z
Jake Mannix
Hey Ted,
<br><br> I'll try out the patch, but I doubt it duplicates any of the stuff I've
<br>got coming in - I've
<br>been meaning to put together an SGD impl, but while ideologically it
<br>overlaps with some
<br>of my decomposition stuff (and the current in-memory SVD which is in Taste
<br>is actually
<br>of the SGD variety, so there may be some overlap with that) but any scalable
<br>impl of
<br>that would be awesome.
<br><br> But this patch is for SGD for logistic regression, right? How
<br>customizable is it for
<br>solving different plugged in optimization functions? I guess I could just
<br>try it out and
<br>see, eh?
<br><br> -jake
<br><br><br>On Wed, Dec 23, 2009 at 12:52 PM, Ted Dunning <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907504&i=0" target="_top" rel="nofollow">ted.dunning@...</a>> wrote:
<br><div class='shrinkable-quote'><br>> Jake,
<br>>
<br>> I would appreciate your comments on this, especially in light of any
<br>> duplication.
<br>>
<br>> David,
<br>>
<br>> If you have any time, your comments are always very welcome as well.
<br>>
<br>> On Wed, Dec 23, 2009 at 12:50 PM, Ted Dunning (JIRA) <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907504&i=1" target="_top" rel="nofollow">jira@...</a>
<br>> >wrote:
<br>>
<br>> >
<br>> > [
<br>> >
<br>> <a href="https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a><br>> ]
<br>> >
<br>> > Ted Dunning updated MAHOUT-228:
<br>> > -------------------------------
<br>> >
<br>> > Fix Version/s: 0.3
<br>> > Status: Patch Available (was: Open)
<br>> >
<br>> > Here is an early implementation. The learning has been implemented, but
<br>> > not tested. Most other aspects are reasonably well tested.
<br>> >
<br>> > > Need sequential logistic regression implementation using SGD techniques
<br>> > > -----------------------------------------------------------------------
<br>> > >
<br>> > > Key: MAHOUT-228
<br>> > > URL: <a href="https://issues.apache.org/jira/browse/MAHOUT-228" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228</a><br>> > > Project: Mahout
<br>> > > Issue Type: New Feature
<br>> > > Components: Classification
<br>> > > Reporter: Ted Dunning
<br>> > > Fix For: 0.3
<br>> > >
<br>> > >
<br>> > > Stochastic gradient descent (SGD) is often fast enough for highly
<br>> > scalable learning (see Vowpal Wabbit, <a href="http://hunch.net/~vw/" target="_top" rel="nofollow">http://hunch.net/~vw/</a><
<br>> <a href="http://hunch.net/%7Evw/" target="_top" rel="nofollow">http://hunch.net/%7Evw/</a>>
<br>> > ).
<br>> > > I often need to have a logistic regression in Java as well, so that is
<br>> a
<br>> > reasonable place to start.
<br>> >
<br>> > --
<br>> > This message is automatically generated by JIRA.
<br>> > -
<br>> > You can reply to this email to add a comment to the issue online.
<br>> >
<br>> >
<br>>
<br>>
<br>> --
<br>> Ted Dunning, CTO
<br>> DeepDyve
<br>>
<br></div><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907456
Re: [math]: how to test sorts
2009-12-23T13:09:48Z
2009-12-23T13:09:48Z
Grant Ingersoll-6
<br>On Dec 23, 2009, at 3:52 PM, Benson Margulies wrote:
<br><div class='shrinkable-quote'><br>>>
<br>>> If you want to test speed, then a pretty easy way is to pick permutations at
<br>>> random, possibly emphasizing some kinds of permutations and run a sort for
<br>>> those permutations using both algorithms. Measuring speeds and taking the
<br>>> fastest iteration for each permutation should allow speed comparisons.
<br>>
<br>> Keep in mind that I am I not changing any algorithms. I want to get
<br>> rid of the deprecations on the call graph of the collections code, if
<br>> nothing else, and that call graph includes a mixed bag of nuts. So,
<br>> what I'm really asking is this: when you all put deprecations on all
<br>> of Colt, what level of testing did you anticipate doing before
<br>> removing them?
<br>>
</div><br>I guess some testing, but by no means complete. Personally, I'd say if you write a test for it that does the reasonable thing (correct output on correct input and maybe some edge testing) then we can remove the deprecation, but just use your best judgment. Beyond that, we could start implementing Clover test coverage, I suppose.<p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907447
Re: Implementing Autocomplete/Query Suggest using Solr
2009-12-23T13:09:14Z
2009-12-23T13:09:14Z
Prasanna R
On Tue, Dec 22, 2009 at 11:49 PM, Shalin Shekhar Mangar <
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907447&i=0" target="_top" rel="nofollow">shalinmangar@...</a>> wrote:
<br><br>>
<br>> > I am curious how an approach that simply uses the wildcard query
<br>> > functionality on an indexed field would work.
<br>>
<br>>
<br>> It works fine as long as the terms are not repeated across documents.
<br>>
<br>>
<br> I do not follow why terms repeating across documents would be an issue. As
<br>long as you can differentiate between multiple matches and rank them
<br>properly it should work right?
<br><br><div class='shrinkable-quote'><br>>
<br>> > While Solr does not support
<br>> > wildcard queries out of the box currently, it will definitely be included
<br>> > in
<br>> > the future and I believe the edismax parser already lets you do that.
<br>>
<br>>
<br>> Solr supports prefix queries and there's a reverse wild card filter in
<br>> trunk
<br>> too.
<br>>
</div><br>Are you referring to facet prefix queries as prefix queries? I looked at
<br>reversed wild card filter but think that the regular wild card matching as
<br>opposed to leading wild card matching is better suited for an
<br>auto-completion feature.
<br><br><br>> We do auto-complete through prefix searches on shingles.
<br>>
<br><br>Just to confirm, do you mean using EdgeNgram filter to produce letter ngrams
<br>of the tokens in the chosen field?
<br><br>Assuming the regular wild card query would also work, any thoughts on how it
<br>compares to the EdgeNGram approach in terms of added indexing cost,
<br>performance, etc.?
<br><br>Thanks a lot for your valuable inputs/comments.
<br><br>Prasanna.
<br><p>From forum: <a href="http://old.nabble.com/Solr---User-f14480.html" embed="fixTarget[14480]" target="_top" >Solr - User</a></p>
tag:old.nabble.com,2006:post-26907440
[jira] Commented: (MAHOUT-78) HBase RowResult/BatchUpdate access via Mahout Vector interface
2009-12-23T13:08:29Z
2009-12-23T13:08:29Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/jira/browse/MAHOUT-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794223#action_12794223" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794223#action_12794223</a> ]
<br><br>Sean Owen commented on MAHOUT-78:
<br>---------------------------------
<br><br>Ted says it might be useful someday. Is this a "Later" issue then, any objections? as usual trying to clean house here, that's all, so we can see what's really on the radar
<br><div class='shrinkable-quote'><br>> HBase RowResult/BatchUpdate access via Mahout Vector interface
<br>> --------------------------------------------------------------
<br>>
<br>> Key: MAHOUT-78
<br>> URL: <a href="https://issues.apache.org/jira/browse/MAHOUT-78" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-78</a><br>> Project: Mahout
<br>> Issue Type: New Feature
<br>> Reporter: Allen Day
<br>> Priority: Minor
<br>> Attachments: hbase.patch
<br>>
<br>>
<br>> An adapter class is attached that allows read/write operations on HBase rows using the Vector interface. This allows, e.g. canopy clustering of rows in an HBase table.
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907297
Re: [math]: how to test sorts
2009-12-23T12:54:21Z
2009-12-23T12:54:21Z
Ted Dunning
Functionality and correctness only. It could even be regression tests, but
<br>we would obviously prefer real tests of correctness.
<br><br>On Wed, Dec 23, 2009 at 12:52 PM, Benson Margulies <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907297&i=0" target="_top" rel="nofollow">bimargulies@...</a>>wrote:
<br><br>> when you all put deprecations on all
<br>> of Colt, what level of testing did you anticipate doing before
<br>> removing them?
<br>>
<br><br><br><br>--
<br>Ted Dunning, CTO
<br>DeepDyve
<br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907279
Re: [jira] Commented: (MAHOUT-78) HBase RowResult/BatchUpdate access via Mahout Vector interface
2009-12-23T12:53:09Z
2009-12-23T12:53:09Z
Ted Dunning
I think that this is in the category of something that sounds very useful,
<br>but I haven't had a need yet.
<br><br>The day after I start using hbase to store things, I would be scrambling for
<br>this, though.
<br><br>On Wed, Dec 23, 2009 at 12:04 PM, Sean Owen (JIRA) <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907279&i=0" target="_top" rel="nofollow">jira@...</a>> wrote:
<br><div class='shrinkable-quote'><br>>
<br>> [
<br>> <a href="https://issues.apache.org/jira/browse/MAHOUT-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794200#action_12794200" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794200#action_12794200</a>]
<br>>
<br>> Sean Owen commented on MAHOUT-78:
<br>> ---------------------------------
<br>>
<br>> Looks like some substantive work here -- is it still relevant and desirable
<br>> to bring this in?
<br>>
<br>> > HBase RowResult/BatchUpdate access via Mahout Vector interface
<br>> > --------------------------------------------------------------
<br>> >
<br>> > Key: MAHOUT-78
<br>> > URL: <a href="https://issues.apache.org/jira/browse/MAHOUT-78" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-78</a><br>> > Project: Mahout
<br>> > Issue Type: New Feature
<br>> > Reporter: Allen Day
<br>> > Priority: Minor
<br>> > Attachments: hbase.patch
<br>> >
<br>> >
<br>> > An adapter class is attached that allows read/write operations on HBase
<br>> rows using the Vector interface. This allows, e.g. canopy clustering of
<br>> rows in an HBase table.
<br>>
<br>> --
<br>> This message is automatically generated by JIRA.
<br>> -
<br>> You can reply to this email to add a comment to the issue online.
<br>>
<br>>
</div><br><br>--
<br>Ted Dunning, CTO
<br>DeepDyve
<br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907270
Re: [math]: how to test sorts
2009-12-23T12:52:36Z
2009-12-23T12:52:36Z
bimargulies
>
<br>> If you want to test speed, then a pretty easy way is to pick permutations at
<br>> random, possibly emphasizing some kinds of permutations and run a sort for
<br>> those permutations using both algorithms. Measuring speeds and taking the
<br>> fastest iteration for each permutation should allow speed comparisons.
<br><br>Keep in mind that I am I not changing any algorithms. I want to get
<br>rid of the deprecations on the call graph of the collections code, if
<br>nothing else, and that call graph includes a mixed bag of nuts. So,
<br>what I'm really asking is this: when you all put deprecations on all
<br>of Colt, what level of testing did you anticipate doing before
<br>removing them?
<br><div class='shrinkable-quote'><br>>
<br>> The down side of this is that you wind up with a pretty slow test. If the
<br>> speed difference isn't large, then the test won't even be very reliable. I
<br>> think that the better option is to test off-line to verify the improvement
<br>> and just make a note in the javadocs with the results.
<br>>
<br>> On Wed, Dec 23, 2009 at 10:27 AM, Benson Margulies <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907270&i=0" target="_top" rel="nofollow">bimargulies@...</a>>wrote:
<br>>
<br>>> On Wed, Dec 23, 2009 at 1:24 PM, Benson Margulies <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907270&i=1" target="_top" rel="nofollow">bimargulies@...</a>>
<br>>> wrote:
<br>>> > '4' was lame humor. Thanks for the concrete suggestion, I'll go there.
<br>>>
<br>>> To be clearer about the lame joke: it's easy to test 'does it sort'.
<br>>> It's hard to test, 'does it correctly get implement this particular
<br>>> variation on quickSort which can be distinguished from others only by
<br>>> speed.'
<br>>>
<br>>>
<br>>>
<br>>
<br></div><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907269
Re: [jira] Updated: (MAHOUT-228) Need sequential logistic regression implementation using SGD techniques
2009-12-23T12:52:06Z
2009-12-23T12:52:06Z
Ted Dunning
Jake,
<br><br>I would appreciate your comments on this, especially in light of any
<br>duplication.
<br><br>David,
<br><br>If you have any time, your comments are always very welcome as well.
<br><br>On Wed, Dec 23, 2009 at 12:50 PM, Ted Dunning (JIRA) <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907269&i=0" target="_top" rel="nofollow">jira@...</a>>wrote:
<br><div class='shrinkable-quote'><br>>
<br>> [
<br>> <a href="https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a>]
<br>>
<br>> Ted Dunning updated MAHOUT-228:
<br>> -------------------------------
<br>>
<br>> Fix Version/s: 0.3
<br>> Status: Patch Available (was: Open)
<br>>
<br>> Here is an early implementation. The learning has been implemented, but
<br>> not tested. Most other aspects are reasonably well tested.
<br>>
<br>> > Need sequential logistic regression implementation using SGD techniques
<br>> > -----------------------------------------------------------------------
<br>> >
<br>> > Key: MAHOUT-228
<br>> > URL: <a href="https://issues.apache.org/jira/browse/MAHOUT-228" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228</a><br>> > Project: Mahout
<br>> > Issue Type: New Feature
<br>> > Components: Classification
<br>> > Reporter: Ted Dunning
<br>> > Fix For: 0.3
<br>> >
<br>> >
<br>> > Stochastic gradient descent (SGD) is often fast enough for highly
<br>> scalable learning (see Vowpal Wabbit, <a href="http://hunch.net/~vw/" target="_top" rel="nofollow">http://hunch.net/~vw/</a><<a href="http://hunch.net/%7Evw/" target="_top" rel="nofollow">http://hunch.net/%7Evw/</a>>
<br>> ).
<br>> > I often need to have a logistic regression in Java as well, so that is a
<br>> reasonable place to start.
<br>>
<br>> --
<br>> This message is automatically generated by JIRA.
<br>> -
<br>> You can reply to this email to add a comment to the issue online.
<br>>
<br>>
</div><br><br>--
<br>Ted Dunning, CTO
<br>DeepDyve
<br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907261
Re: [jira] Commented: (MAHOUT-173) Implement clustering of massive-domain attributes
2009-12-23T12:51:15Z
2009-12-23T12:51:15Z
Ted Dunning
I never saw much progress on this.
<br><br>On Wed, Dec 23, 2009 at 11:58 AM, Sean Owen (JIRA) <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907261&i=0" target="_top" rel="nofollow">jira@...</a>> wrote:
<br><div class='shrinkable-quote'><br>>
<br>> [
<br>> <a href="https://issues.apache.org/jira/browse/MAHOUT-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794197#action_12794197" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794197#action_12794197</a>]
<br>>
<br>> Sean Owen commented on MAHOUT-173:
<br>> ----------------------------------
<br>>
<br>> Pinging this issue -- is there any progress in the past 3.5 months or
<br>> should we shelve it?
<br>>
<br>> > Implement clustering of massive-domain attributes
<br>> > -------------------------------------------------
<br>> >
<br>> > Key: MAHOUT-173
<br>> > URL: <a href="https://issues.apache.org/jira/browse/MAHOUT-173" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-173</a><br>> > Project: Mahout
<br>> > Issue Type: New Feature
<br>> > Components: Clustering
<br>> > Reporter: Matias Bjørling
<br>> > Priority: Trivial
<br>> > Original Estimate: 30h
<br>> > Remaining Estimate: 30h
<br>> >
<br>> > Implement the Clustering algorithm described in "A Framework for
<br>> Clustering Massive-Domain Data Streams" by Chary C. Aggarwal.
<br>> > Steps:
<br>> > 1. Implement baseline solution to compare solutions.
<br>> > 2. Figure out how to implement the loading of clustering by looking at
<br>> the k-means implementation.
<br>> > 3. Implement Count-Min sketch algorithm for each cluster.
<br>> > 4. Find out how to give the user the power to choose the distance
<br>> function for the input data ( Maybe already possible? )
<br>>
<br>> --
<br>> This message is automatically generated by JIRA.
<br>> -
<br>> You can reply to this email to add a comment to the issue online.
<br>>
<br>>
</div><br><br>--
<br>Ted Dunning, CTO
<br>DeepDyve
<br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907250
[jira] Updated: (MAHOUT-228) Need sequential logistic regression implementation using SGD techniques
2009-12-23T12:50:29Z
2009-12-23T12:50:29Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ]
<br><br>Ted Dunning updated MAHOUT-228:
<br>-------------------------------
<br><br> Fix Version/s: 0.3
<br> Status: Patch Available (was: Open)
<br><br>Here is an early implementation. The learning has been implemented, but not tested. Most other aspects are reasonably well tested.
<br><div class='shrinkable-quote'><br>> Need sequential logistic regression implementation using SGD techniques
<br>> -----------------------------------------------------------------------
<br>>
<br>> Key: MAHOUT-228
<br>> URL: <a href="https://issues.apache.org/jira/browse/MAHOUT-228" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/MAHOUT-228</a><br>> Project: Mahout
<br>> Issue Type: New Feature
<br>> Components: Classification
<br>> Reporter: Ted Dunning
<br>> Fix For: 0.3
<br>>
<br>>
<br>> Stochastic gradient descent (SGD) is often fast enough for highly scalable learning (see Vowpal Wabbit, <a href="http://hunch.net/~vw/" target="_top" rel="nofollow">http://hunch.net/~vw/</a>).
<br>> I often need to have a logistic regression in Java as well, so that is a reasonable place to start.
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><p>From forum: <a href="http://old.nabble.com/Mahout-Developer-List-f32041.html" embed="fixTarget[32041]" target="_top" >Mahout Developer List</a></p>
tag:old.nabble.com,2006:post-26907226
[jira] Commented: (LUCENE-2179) CharArraySet.clear()
2009-12-23T12:48:29Z
2009-12-23T12:48:29Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/jira/browse/LUCENE-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794218#action_12794218" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/LUCENE-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794218#action_12794218</a> ]
<br><br>Uwe Schindler commented on LUCENE-2179:
<br>---------------------------------------
<br><br>For this to work, in BW branch the clear() test will be disabled.
<br><div class='shrinkable-quote'><br>> CharArraySet.clear()
<br>> --------------------
<br>>
<br>> Key: LUCENE-2179
<br>> URL: <a href="https://issues.apache.org/jira/browse/LUCENE-2179" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/LUCENE-2179</a><br>> Project: Lucene - Java
<br>> Issue Type: Improvement
<br>> Components: Analysis
<br>> Reporter: Robert Muir
<br>> Assignee: Uwe Schindler
<br>> Priority: Minor
<br>> Fix For: 3.1
<br>>
<br>> Attachments: LUCENE-2179.patch
<br>>
<br>>
<br>> I needed CharArraySet.clear() for something I was working on in Solr in a tokenstream.
<br>> instead I ended up using CharArrayMap<Boolean> because it supported .clear()
<br>> it would be better to use a set though, currently it will throw UOE for .clear() because AbstractSet will call iterator.remove() which throws UOE.
<br>> In Solr, the very similar CharArrayMap.clear() looks like this:
<br>> {code}
<br>> @Override
<br>> public void clear() {
<br>> count = 0;
<br>> Arrays.fill(keys,null);
<br>> Arrays.fill(values,null);
<br>> }
<br>> {code}
<br>> I think we can do a similar thing as long as we throw UOE for the UnmodifiableCharArraySet
<br>> will submit a patch later tonight (unless someone is bored and has nothing better to do)
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907226&i=0" target="_top" rel="nofollow">java-dev-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26907226&i=1" target="_top" rel="nofollow">java-dev-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/Lucene---Java-Developer-f46.html" embed="fixTarget[46]" target="_top" >Lucene - Java Developer</a></p>
tag:old.nabble.com,2006:post-26906999
[jira] Commented: (LUCENE-2179) CharArraySet.clear()
2009-12-23T12:26:29Z
2009-12-23T12:26:29Z
JIRA jira@apache.org
<br> [ <a href="https://issues.apache.org/jira/browse/LUCENE-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794208#action_12794208" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/LUCENE-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794208#action_12794208</a> ]
<br><br>Uwe Schindler commented on LUCENE-2179:
<br>---------------------------------------
<br><br>I will commit this together with LUCENE-2169.
<br><div class='shrinkable-quote'><br>> CharArraySet.clear()
<br>> --------------------
<br>>
<br>> Key: LUCENE-2179
<br>> URL: <a href="https://issues.apache.org/jira/browse/LUCENE-2179" target="_top" rel="nofollow">https://issues.apache.org/jira/browse/LUCENE-2179</a><br>> Project: Lucene - Java
<br>> Issue Type: Improvement
<br>> Components: Analysis
<br>> Reporter: Robert Muir
<br>> Assignee: Uwe Schindler
<br>> Priority: Minor
<br>> Fix For: 3.1
<br>>
<br>> Attachments: LUCENE-2179.patch
<br>>
<br>>
<br>> I needed CharArraySet.clear() for something I was working on in Solr in a tokenstream.
<br>> instead I ended up using CharArrayMap<Boolean> because it supported .clear()
<br>> it would be better to use a set though, currently it will throw UOE for .clear() because AbstractSet will call iterator.remove() which throws UOE.
<br>> In Solr, the very similar CharArrayMap.clear() looks like this:
<br>> {code}
<br>> @Override
<br>> public void clear() {
<br>> count = 0;
<br>> Arrays.fill(keys,null);
<br>> Arrays.fill(values,null);
<br>> }
<br>> {code}
<br>> I think we can do a similar thing as long as we throw UOE for the UnmodifiableCharArraySet
<br>> will submit a patch later tonight (unless someone is bored and has nothing better to do)
</div><br>--
<br>This message is automatically generated by JIRA.
<br>-
<br>You can reply to this email to add a comment to the issue online.
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26906999&i=0" target="_top" rel="nofollow">java-dev-unsubscribe@...</a>
<br>For additional commands, e-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26906999&i=1" target="_top" rel="nofollow">java-dev-help@...</a>
<br><br><p>From forum: <a href="http://old.nabble.com/Lucene---Java-Developer-f46.html" embed="fixTarget[46]" target="_top" >Lucene - Java Developer</a></p>