Thanks.  

Agreed, that would be cool. 

I reindexed from source though, not directly from FAST.

Tim

-----Original Message-----
From: Otis Gospodnetic [mailto:[EMAIL PROTECTED] 
Sent: Sunday, February 17, 2008 11:44 PM
To: [email protected]
Subject: Re: Solr Perl Interface

Very nice, Tim.  But that FAST->Solr document collection transfer would
also be cool to see and have/use for those lucky FAST customers who want
to quickly give Solr a try with their existing data.

Otis 

--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch

----- Original Message ----
> From: Timothy Garafola <[EMAIL PROTECTED]>
> To: [email protected]
> Sent: Friday, February 15, 2008 4:47:19 PM
> Subject: Solr Perl Interface
> 
> I recently released a simple perl wrapper module to CPAN which
supplies
> methods in perl for posting adds, deletes, commits, and optimizes to a
> solr server.  Originally I had written some simple processes to handle
> this when porting a large collection of documents from FAST into SOLR.
> Mark Backman and Yousef Ourabi suggested that I take this a step
further
> and submit something to the open source community.  So now it's
> available for download at via
> http://search.cpan.org/author/GARAFOLA/Solr-0.03/lib/Solr.pm.
> 
>  
> 
> As time permits, I'm adding to this.  I also welcome contributions and
> hope to release the first updated version in a week or so.  Yousef has
> stated interest in extending it to supply querying functionality.  
> 
>  
> 
> One of the things I have a need for is the ability to update by query;
> something similar in functionality to SOLRs delete_by_query.  Is there
> anything like this already in SOLR?    I'm playing with doing this in
> perl by first issuing a query, parsing the returned xml into  a perl
> data structure, updating element values and/or extending it with
dynamic
> fields in the data structure, then reposting the docs returned in the
> initial query.  Can anyone tell me if I'm reinventing a wheel here or
> suggest an alternative approach?
> 
>  
> 
> Thanks,
> 
> Tim Garafola
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> 


Reply via email to