More attributes for indexing?
Hi folks, At the last RIPE meeting there was some discussion about which attributes would be useful to keep indices on. Well, since our office move last weekend, I came up with a (rather predictable) one: $ whois -i ad "Lockton House" % ignored attribute "address" since it is not indexed as a reference % no attributes specified for -i query $ _ Dang! It would be nice to have an index on address, although such an index might become veeerrrry large, due to the fact that you can specify multiple "address" attributes per object; dunno. Any thoughts? Cheers, Steven
As a temporary workaround, telnet to info.ripe.net, select WAIS, select ripe-database and search on lockton. It's not perfect and it's ugly, but it works. Having some experience with lynx helps ;-) For those with WAIS clients installed, have a look at ftp://ftp.ripe.net/ripe/wais-sources/* Geert Jan On Mon, 30 Sep 1996 17:43:27 +0100 Steven Bakker wrote:
Hi folks,
At the last RIPE meeting there was some discussion about which attributes would be useful to keep indices on. Well, since our office move last weekend, I came up with a (rather predictable) one:
$ whois -i ad "Lockton House"
% ignored attribute "address" since it is not indexed as a reference
% no attributes specified for -i query
$ _
Dang! It would be nice to have an index on address, although such an index might become veeerrrry large, due to the fact that you can specify multiple "address" attributes per object; dunno.
Any thoughts?
Cheers, Steven
Quoting from Geert Jan de Groot's message:
As a temporary workaround, telnet to info.ripe.net, select WAIS, select ripe-database and search on lockton.
It's not perfect and it's ugly, but it works. Having some experience with lynx helps ;-)
You can also use a user friendly WAIS interface to the RIPE database at http://www.nis.garr.it/cgi-bin/HY/rc?/who/conf Click on RIPE-NCC database located at GARR/NIS and on continue button Then you can either search for specific fields or full-text or combine them with logic operators. Cheers, Blasco
For those with WAIS clients installed, have a look at ftp://ftp.ripe.net/ripe/wais-sources/*
Geert Jan
On Mon, 30 Sep 1996 17:43:27 +0100 Steven Bakker wrote:
Hi folks,
At the last RIPE meeting there was some discussion about which attributes would be useful to keep indices on. Well, since our office move last weekend, I came up with a (rather predictable) one:
$ whois -i ad "Lockton House"
% ignored attribute "address" since it is not indexed as a reference
% no attributes specified for -i query
$ _
Dang! It would be nice to have an index on address, although such an index might become veeerrrry large, due to the fact that you can specify multiple "address" attributes per object; dunno.
Any thoughts?
Cheers, Steven
-- ---------- ---------- Antonio-Blasco Bonito E-Mail: bonito@nis.garr.it GARR - Network Information Service c=it;a=garr;p=garr;o=nis;s=bonito c/o CNUCE - Istituto del CNR Tel: +39 50 593246 Via S. Maria, 36 Fax: +39 50 904052 I-56126 PISA Telex: 500371 CNUCE I Italy Url: http://www.nis.garr.it/nis/staff/bonito.html ---------- ----------
Hi Steven,
Steven Bakker writes :
At the last RIPE meeting there was some discussion about which attributes would be useful to keep indices on. Well, since our office move last weekend, I came up with a (rather predictable) one:
$ whois -i ad "Lockton House"
% ignored attribute "address" since it is not indexed as a reference
% no attributes specified for -i query
$ _
It would be nice to have an index on address, although such an index might become veeerrrry large, due to the fact that you can specify multiple "address" attributes per object; dunno.
Any thoughts?
From the technical point of view:
This is very well possible. Indexing the person objects takes about 1.5 hour. This extra indexing might cause 3 times more indexed values (for person objects only) and thus will probably take about 4.5 hours at this point in time (yes, indexing times are *not* scaling exponentially anymore since the last release ;-)). This means that it could be done on the current machine for the next year and even for a longer term if indexing is done in the weekend. A on-the-fly reindexing feature could solve this problem completely. Note that much of this is harddisk speed bounded and is thus more difficult to speed up then just buying a faster CPU. One warning though, the perl/dbm package might give problems earlier in time, which could make it necessary to withdraw this functionality later in the future. David K. ---
participants (4)
-
Antonio_Blasco Bonito -
davidk＠isi.edu -
Geert Jan de Groot -
Steven Bakker