Haven't started using it yet. Need to do searching via SQL large amounts of text data in DB2 table. Normally in MS SQL Server I'd turn on full text indexing in a few minutes on the table in question and using the CONTAINS and CONTAINSTABLE SQL commands, but it seems much more involved on the IBM I using an externally (PASE Hosted) service that you install separately, configured, maintain, and schedule index update jobs. Adding synonyms also requires XML and command line. SOOOO MUCH easier in MS SQL Server.
From: Richard Schoen [mailto:Richard.Schoen@xxxxxxxxxxxxxxx]
Sent: Friday, September 25, 2015 9:33 AM
Subject: RE: Any alternative to OmniFind?
You could look at Apache Solr perhaps.
How are you guys using Omnifind ?
Does it work well ?
Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems richard.schoen@xxxxxxxxxxxxxxx www.rjssoftware.com Visit me on: Twitter | LinkedIn
date: Fri, 25 Sep 2015 14:16:35 +0000
from: Matt Olson <Matt.Olson@xxxxxxxx>
subject: Any alternative to OmniFind?
Is there any alternative to OmniFind for the IBM i?
In Microsoft SQL Server we have full text search built directly into the database. This affords some very nice possibilities such as immediate indexing upon update/insert so you know the search index is always up to date.
However on the IBM i it is not integrated into the database, and the search indexing is a scheduled affair with the minimum re-index time set to 5 minutes. Meaning the search index can be 5 minutes out of date.
Is there a more real-time solution for IBM i?
Does the 5 minute re-index rebuild the entire index or is it an incremental index?
This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact