API(3pm) | User Contributed Perl Documentation | API(3pm) |
SWISH::API - Perl interface to the Swish-e C Library
use SWISH::API; my $swish = SWISH::API->new( 'index.swish-e' ); $swish->abort_last_error if $swish->Error; # A short-cut way to search my $results = $swish->query( "foo OR bar" ); # Or more typically my $search = $swish->new_search_object; # then in a loop my $results = $search->execute( $query ); # always check for errors (but aborting is not always necessary) $swish->abort_last_error if $swish->Error; # Display a list of results my $hits = $results->hits; if ( !$hits ) { print "No Results\n"; return; /* for example *. } print "Found ", $results->hits, " hits\n"; # Seek to a given page - should check for errors $results->seek_result( ($page-1) * $page_size ); while ( my $result = $results->next_result ) { printf("Path: %s\n Rank: %lu\n Size: %lu\n Title: %s\n Index: %s\n Modified: %s\n Record #: %lu\n File #: %lu\n\n", $result->property( "swishdocpath" ), $result->property( "swishrank" ), $result->property( "swishdocsize" ), $result->property( "swishtitle" ), $result->property( "swishdbfile" ), $result->result_property_str( "swishlastmodified" ), $result->property( "swishreccount" ), $result->property( "swishfilenum" ) ); } # display properties and metanames for my $index_name ( $swish->index_names ) { my @metas = $swish->meta_list( $index_name ); my @props = $swish->property_list( $index_name ); for my $m ( @metas ) { my $name = $m->name; my $id = $m->id; my $type = $m->type; } # (repeat above for @props) }
This module provides a Perl interface to the Swish-e search engine. This module allows embedding the swish-e search code into your application avoiding the need to fork to run the swish-e binary and to keep an index file open when running multiple queries. This results in increased search performance.
You must have installed Swish-e version 2.4 before building this module. Download from:
http://swish-e.org
This module includes a number of classes.
Searching consists of connecting to a swish-e index (or indexes), and then running queries against the open index. Connecting to the index creates a swish object blessed into the SWISH::API class.
A SWISH::API::Search object is created from the SWISH::API object. The SWISH::API::Search object can have associated parameters (e.g. result sort order).
The SWISH::API::Search object is used to query the associated index file or files. A query on a search object returns a results object of the class SWISH::API::Results. Then individual results of the SWISH::API::Result class can be fetched by calling a method of the results object.
Finally, a result's properties can be accessed by calling methods on the result object.
To begin using Swish you must first create a Swish Handle object. This object makes the connection to one or more index files and is used to create objects used for searching the associated index files.
Returns the header value for the header and index file specified. Most headers are a single item, but some headers (e.g. "Stopwords") return a list.
The list of possible header names can be obtained from the Swishheader_names method.
Error Handling
All errors are stored in and accessed via the SWISH::API object (the Swish Handle). That is, even an error that occurs when calling a method on a result (SWISH::API::Result) object will store the error in the parent SWISH:API object.
Check for errors after every method call. Some errors are critical errors and will require destruction of the SWISH::API object. Critical errors will typically only happen when attaching to the database and are errors such as an invalid index file name, permissions errors, or passing invalid objects to calls.
Typically, if you receive an error when attaching to an index file or files you should assume that the error is critical and let the swish object fall out of scope (and destroyed). Otherwise, if an error is detected you should check if it is a critical error. If the error is not critical you may continue using the objects that have been created (for example, an invalid meta name will generate a non-critical error, so you may continue searching using the same search object).
Error state is cleared upon a new query.
Again, all error methods need to be called on the parent swish object
badmeta=foo
and "badmeta" is an invalid metaname $swish->error_string might return "Unknown metaname", but $swish->last_error_msg might return "badmeta".
Generating Search and Result Objects
See the section on "SWISH::API::Search" for methods available on the returned object.
The advantage of this method is that a search object can be used for multiple queries:
$search = $swish->New_Search_Objet; while ( $query = next_query() ) { $results = $search->execute( $query ); ... }
This method basically is the equivalent of
$results = $swish->new_search_object->execute( $query );
A search object holds the parameters used to generate a list of results. These methods are used to adjust these parameters and to create the list of results for the current set of search parameters.
A "structure" is a bit-mapped flag used to limit search results to specific parts of an HTML document, such as the title or in H tags. The possible bits are:
IN_FILE = 1 This is the default IN_TITLE = 2 In <title> tag IN_HEAD = 4 In <head> tag IN_BODY = 8 In <body> IN_COMMENTS = 16 In html comments IN_HEADER = 32 In <h*> IN_EMPHASIZED = 64 In <em>, <b>, <strong>, <i> IN_META = 128 In a meta tag (e.g. not swishdefault)
So if you wish to limit your searches to words in heading tags (e.g. <H1>) or in the <title> tag use:
$search->set_structure( IN_HEAD | IN_TITLE );
For example to limit searches to documents modified in the last 48 hours:
my $start = time - 48 * 60 * 60; $search->set_search_limit( 'swishlastmodified', $start, time() );
An error will be set if the property has already been specified or if $high < $low.
Other errors may not be reported until running the query, such as the property name is invalid or if $low or $high are not numeric and the property specified is a numeric property.
Once a query is run you cannot change the limit settings for the search object without calling the reset_search_limit method first.
For example, to sort the results by path name in ascending order and by rank in descending order:
$search->set_sort( 'swishdocpath asc swishrank desc' );
The "asc" and "desc" qualifiers are optional, and if omitted ascending is assumed.
Currently, errors (e.g invalid property name) are not detected on this call, but rather when executing a query. This may change in the future.
Searching generates a results object blessed into the SWISH::API::Results class.
A typical use would be to create a search object once and then call this method for each query using the same search object changing only the passed in $query.
The caller should check for errors after making this all.
A query creates a results object that contains information about the query (e.g. number of hits) and access to the individual results.
$index_name must match one of the index files specified on the creation of the swish object (via the SWISH::API->new call).
The parsed words are useful for highlighting search terms in associated documents.
$index_name must match one of the index files specified on the creation of the swish object (via the SWISH::API->new call).
Useful for seeking to a specific "page" of results.
The follow methods provide access to data related to an individual result.
Can return undefined.
Date properties are returned as a timestamp. Use something like Date::Format to format the strings (or just call scalar localtime( $prop ) ).
Undefined values are returned at the null string ("").
Pass in the name of an open index file name and returns a list of SWISH::API::MetaName objects. Three methods are currently defined on these objects:
$meta->name; $meta->id; $meta->type;
Name returns the name of the meta as defined in the MetaNames config option when the index was created.
The id is the internal ID number used to represent the meta name.
type is the type of metaname. Currently only one type exists and its value is zero.
Pass in the name of an open index file name and returns a list of SWISH::API::MetaName objects. Three methods are currently defined on these objects:
$prop->name; $prop->id; $prop->type;
name returns the name of the meta as defined in the MetaNames config option when the index was created.
The id is the internal ID number used to represent the meta name.
type is the type of metaname. Currently only one type exists and its value is zero.
Returns the stemmed version of the passed in word.
Deprecated because only stems using the original Porter Stemmer and uses a shared memory location in the SW_HANDLE object to store the stemmed word. See below for other stemming options.
In the event that a word does not stem (e.g. trying to stem a number), this method will return the original input word specified when $result->fuzzy_word( $word ) was called.
Splits up the input string into tokens of swish words and operators.
Perl's garbage collection makes it easy to write code for searching with Swish-e, but care must be taken not to keep objects around too long which can use up memory.
Here's an example of a potential problem. Say you have a very large number of documents indexed and you want to find the first hit for a number of popular keywords (error checking omitted in this bad example):
sub first_hit { my $query = shift; my $handle = SWISH::API->new( 'index.swish-e'); my $results = $handle->query( $query ); my $first_hit = $results->next_result; return $first_hit; } my @first_hit_list; for ( @keywords ) push @first_hit_list, $first_hit($_); }
The first_hit() subroutine is returning a SWISH::Result object. That makes it easy to access properties:
# print file names for my $result ( @first_hit_list ) { print $result->property('swishdocpath'),"\n"; }
But as long as a SWISH::API::Result object is around, so is the entire list of results generated by the $handle->query() call, and the index file is still open (because a SWISH::API::Result depends on a SWISH::API::Results object, which depends on a SWISH::API object).
In this case it would be better to return from first_hit() just the properties you need:
... my $first_hit = $results->next_result; return $first_hit->property('swishdocpath'); }
Then when first_hit() sub ends the result list will be freed, and the index file closed, thanks to Perl's reference count tracking.
Note: the other problem with the above code is that the same index file is opened for each call to the function. Don't do that, instead open the index file once.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
Bill Moseley moseley@hank.org. 2002/2003/2004
Please contact the Swish-e discussion email list for support with this module or with Swish-e. Please do not contact the developers directly.
2022-10-20 | perl v5.36.0 |