Efficiency Network Security Analysis for Data Mining
I see this all the time, and so I'm used to it; but sometimes it is fun to post it anyway, since this is dated just a week ago, and today flew into my inbox;
I'm auditing UID consistency across our hosts, and have created the following datafile, consisting of four fields. I would like to get a count of the combination of the last two fields. ie: I would like to find out how many instances there are of "root 0" and how many of "uucp 5", for every line... (3 Replies)
Discussion started by: akbar
3 Replies
LEARN ABOUT DEBIAN
kinosearch1::analysis::polyanalyzer
KinoSearch1::Analysis::PolyAnalyzer(3pm) User Contributed Perl Documentation KinoSearch1::Analysis::PolyAnalyzer(3pm)NAME
KinoSearch1::Analysis::PolyAnalyzer - multiple analyzers in series
SYNOPSIS
my $analyzer = KinoSearch1::Analysis::PolyAnalyzer->new(
language => 'es',
);
# or...
my $analyzer = KinoSearch1::Analysis::PolyAnalyzer->new(
analyzers => [
$lc_normalizer,
$custom_tokenizer,
$snowball_stemmer,
],
);
DESCRIPTION
A PolyAnalyzer is a series of Analyzers -- objects which inherit from KinoSearch1::Analysis::Analyzer -- each of which will be called upon
to "analyze" text in turn. You can either provide the Analyzers yourself, or you can specify a supported language, in which case a
PolyAnalyzer consisting of an LCNormalizer, a Tokenizer, and a Stemmer will be generated for you.
Supported languages:
en => English,
da => Danish,
de => German,
es => Spanish,
fi => Finnish,
fr => French,
it => Italian,
nl => Dutch,
no => Norwegian,
pt => Portuguese,
ru => Russian,
sv => Swedish,
CONSTRUCTOR
new()
my $analyzer = KinoSearch1::Analysis::PolyAnalyzer->new(
language => 'en',
);
Construct a PolyAnalyzer object. If the parameter "analyzers" is specified, it will override "language" and no attempt will be made to
generate a default set of Analyzers.
o language - Must be an ISO code from the list of supported languages.
o analyzers - Must be an arrayref. Each element in the array must inherit from KinoSearch1::Analysis::Analyzer. The order of the
analyzers matters. Don't put a Stemmer before a Tokenizer (can't stem whole documents or paragraphs -- just individual words), or a
Stopalizer after a Stemmer (stemmed words, e.g. "themselv", will not appear in a stoplist). In general, the sequence should be:
normalize, tokenize, stopalize, stem.
COPYRIGHT
Copyright 2005-2010 Marvin Humphrey
LICENSE, DISCLAIMER, BUGS, etc.
See KinoSearch1 version 1.00.
perl v5.14.2 2011-11-15 KinoSearch1::Analysis::PolyAnalyzer(3pm)
02-28-2020
