Hi Jose,

Your code likely would still work, but it may be easier to simply enable the "search" index event consumer (this is the one that refreshes a Lucene index).

By default, 5.x has this list of event consumers enabled in dspace.cfg:

event.dispatcher.default.consumers = versioning, discovery, eperson, harvester

The "discovery" consumer ensures Discovery (Solr) reindexes when changes occur. You could just append the "search" consumer to similarly notify Lucene, e.g.

event.dispatcher.default.consumers = versioning, discovery, eperson, harvester, search

Adding "search" to that list triggers this SearchConsumer whenever changes to Community, Collection & Items occur (including when filter-media runs)
https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/search/SearchConsumer.java

- Tim

On 2/25/2016 8:55 AM, Jose Blanco wrote:
Thanks Tim for your response. What I have done is I have left the advance page from previous Dspace instances with Lucene, but everything else is Discovery. This page uses lucene:

https://deepblue.lib.umich.edu/advanced-search

and so does the box on the menu bar from the main page:

https://deepblue.lib.umich.edu/

So I'm using some old code to get this functionality.

Now, in the past I had the code from my previous email in the filter-media so that the full text search for the lucene index would be updated. When I did the last code merge I chopped that code out, and am now realizing that I need to put it back in if I the lucene full text search to work. What do you think?

Thanks again!
Jose





On Thu, Feb 25, 2016 at 9:32 AM, Tim Donohue <tdono...@duraspace.org <mailto:tdono...@duraspace.org>> wrote:

    Hi Jose,

    Could you describe your setup more?  It's not actually possible
    (well not recommended) to run Discovery (which uses Apache Solr)
AND Lucene (which is a separate search interface) simultaneously. Are you running Discovery, or are you running the traditional
    Lucene-based search?  By default, DSpace 5.x uses Discovery.

    https://wiki.duraspace.org/display/DSDOC5x/Discovery

    If you are running Discovery, then it is notified of any updates
to items, etc. and will reindex individual items when notified. There's no need to add any special code for that.

    If you are still using Lucene, you might want to think about
    whether it's worth moving to just using Discovery. In 5.x, we
    deprecated Lucene searching, and it is being removed entirely in
    6.x (coming soon).  So, while you can still use Lucene in 5.x,
    you'll eventually need to move to using Discovery (with Solr) once
    6.x is released.

    - Tim


    On 2/24/2016 3:46 PM, Jose Blanco wrote:
    I am currently using lucene and discovery in 5.1.  In 4.2 I had
    this bit of code in MediaFilterManager.java so that when ./dsapce
    filter-media ran the lucene index would be updated.  I wonder if
    it will work in 5.1 and if perhaps there is a better way to do
    it.  This is the code I had:

                if (updateIndex)
                {
                    if (!isQuiet)
                    {
    System.out.println("Updating search index:");
                    }
    DSIndexer.setBatchProcessingMode(true);
                    try
                    {
    DSIndexer.updateIndex(c);
                    }
                    finally
                    {
    DSIndexer.setBatchProcessingMode(false);
                    }
                }

    Thank you!
    Jose
-- You received this message because you are subscribed to the
    Google Groups "DSpace Technical Support" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to dspace-tech+unsubscr...@googlegroups.com
    <mailto:dspace-tech+unsubscr...@googlegroups.com>.
    To post to this group, send email to dspace-tech@googlegroups.com
    <mailto:dspace-tech@googlegroups.com>.
    Visit this group at https://groups.google.com/group/dspace-tech.
    For more options, visit https://groups.google.com/d/optout.

-- Tim Donohue
    Technical Lead for DSpace & DSpaceDirect
    DuraSpace.org | DSpace.org | DSpaceDirect.org

-- You received this message because you are subscribed to the Google
    Groups "DSpace Technical Support" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to dspace-tech+unsubscr...@googlegroups.com
    <mailto:dspace-tech+unsubscr...@googlegroups.com>.
    To post to this group, send email to dspace-tech@googlegroups.com
    <mailto:dspace-tech@googlegroups.com>.
    Visit this group at https://groups.google.com/group/dspace-tech.
    For more options, visit https://groups.google.com/d/optout.



--
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

--
You received this message because you are subscribed to the Google Groups "DSpace 
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to