Updating my question… it is not the size of the PDF document that affects indexing. It is something else I don’t know?
I submitted two test PDF documents. I was able to convert them to text on my local machine, so they are not protected PDFs. 20 pages 290KB – was NOT indexed by GSearch, running manual indexing did not help. 28 pages 11,50KB – was indexed by GSearch automatically. I tried several times – same result. Serhiy On Thu, Apr 8, 2010 at 4:27 PM, Serhiy Polyakov <[email protected]> wrote: > Bill, > > Thanks! Indeed I see now that GSearch automatic index update is > working with all default parameters (I enabled messaging service when > installing Fedora). > > I think I have different problem now. I have PDF documents in my > collection. I found that when I submit objects with large PDF > (~>250KB) they are not indexed neither auto or manually. I mean > nothing is indexed, neither DC metadata not content of PDF. > > Please advise if you have any idea where to look for solution. > > Thanks, > Serhiy > > > > On Thu, Apr 8, 2010 at 10:15 AM, Bill Branan <[email protected]> wrote: >> Hi Serhiy, >> A messaging client is included with GSearch, so there's no need for you to >> write any code or do any additional builds to set up automatic updates. >> First, look in Fedora's fedora.fcfg file and ensure that under the >> MessagingModule the enabled parameter is set to true. You may also need to >> replace 'localhost' with your Fedora server host name in the >> java.naming.provider.url param. >> Second, look in the updater.properties file under GSearch and ensure that >> the java.naming.provider.url includes the correct host name (it should point >> to your Fedora server host.) If GSearch is running in the same server as >> Fedora, localhost is fine. >> For a basic setup, the default values are fine for the rest of the >> parameters. >> If you are running GSearch in a server separate from Fedora, make sure that >> your Fedora is started before starting GSearch, otherwise the JMS listener >> in GSearch won't be able to connect with the broker which is started when >> Fedora starts. This is assuming you're using the embedded ActiveMQ which is >> provided in Fedora. Otherwise, your JMS broker needs to be started before >> either Fedora or GSearch. >> As a note, the connection.factory.name is not included in the fcfg because >> it is assumed that in most cases it doesn't need to be changed. If you would >> like to use a JMS or JNDI provider other than ActiveMQ (which is the default >> provided by Fedora) then you can add this param to the config file. It >> doesn't sound like that's what you're trying to do. >> Bill >> >> On Thu, Apr 8, 2010 at 4:16 AM, Serhiy Polyakov <[email protected]> wrote: >>> >>> Hello, >>> >>> Is there a simple instruction to setup automatic updates for default >>> Lucene BasicIndex with GSearch 2.2 and Fedora 3.3? >>> >>> I setup Fedora GSearch service and can index repository manually from >>> the browser. I am trying to configure the service for automatic >>> updates. For GSearch everything was already set by default as asked in >>> the Instruction here: >>> >>> http://www.fedora-commons.org/confluence/display/FCSVCS/Generic+Search+Service+2.2#GenericSearchService2.2-sauto >>> >>> Fedora’s messaging service was enabled when I installed Fedora. >>> Fedora’s messaging documentation here: >>> http://www.fedora-commons.org/confluence/display/FCR30/Messaging >>> asks to modify connection.factory.name but this parameter is not in >>> fedora.fcfg file. >>> >>> Also documentation says “To build the Messaging Client, run the >>> messaging-client Ant target from the source distribution”. It gives >>> example of Java code for JmsMessagingClient… >>> >>> It is not clear if I need to write my own JmsMessagingClient…? >>> >>> Thanks, >>> Serhiy >>> >>> >>> ------------------------------------------------------------------------------ >>> Download Intel® Parallel Studio Eval >>> Try the new software tools for yourself. Speed compiling, find bugs >>> proactively, and fine-tune applications for parallel performance. >>> See why Intel Parallel Studio got high marks during beta. >>> http://p.sf.net/sfu/intel-sw-dev >>> _______________________________________________ >>> Fedora-commons-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users >> >> > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Fedora-commons-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
