the Settings menu a font that supports Unicode characters, the
default platform font often doesn't support them, which results in '?'
or other strange characters.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__
s and a happy New Year to you all! :)
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info
ed approach first, because it's
easy to implement, and then see if it's good enough.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embe
regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigra
se the doc enumeration and calculate the
total number of term occurrences in all documents (e.g. in
RIDFTermPruningPolicy.initPositionsTerm(..) ), and use this value in the
formula in place of termPositions.freq().
--
Best regards,
Andrze
On 29/03/2012 11:14, Andrzej Bialecki wrote:
The problem in our implementation is that we use a within-document term
frequency (the number of occurrences of t in the current document) and
not a collection-wide term frequency... so, it looks to me that the fix
would be to first fully traverse
age as far as I know.
LUCENE-3837, to be specific. But as you said, it's still early and there
is no code yet to speak of...
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| I
ct is lower than the current lowest score.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Co
of field:term pairs.
--
Best regards,
Andrzej Bialecki
http://www.sigram.com, blog http://www.sigram.com/blog
___.,___,___,___,_._. __<><
[___||.__|__/|__||\/|: Information Retrieval, System Integration
___|||__||..\|..||..|: Co
g.Stires)
* Issue 19: Custom directory implementation must be inherited from
FSDirectory (mitja.lenic)
* Issue 21: luke tarball needs to extract to a "luke" directory
(bevan.koopman, Photodeus)
* Issue 27: Cannot add or edit documents using StandardAnalyzer
(dean.thrasher)
Thanks to
ds. The
question is whether the space savings would be worth the complication?
--
Best regards,
Andrzej Bialecki
http://www.sigram.com, blog http://www.sigram.com/blog
___.,___,___,___,_._. __<><
[___||.__|__/|__||\/|: Information
at shows a
term vector correctly shows positions and offsets if available (or
blanks if not available).
--
Best regards,
Andrzej Bialecki
http://www.sigram.com, blog http://www.sigram.com/blog
___.,___,___,___,_._. __<><
[_
re it, either using stored fields or in an
external system.
--
Best regards,
Andrzej Bialecki
http://www.sigram.com, blog http://www.sigram.com/blog
___.,___,___,___,_._. __<><
[___||.__|__/|__||\/|: Information Retrieval, System Integration
___|||__||.
e you enjoy the reading. :)
--
Best regards,
Andrzej Bialecki
http://www.sigram.com, blog http://www.sigram.com/blog
___.,___,___,___,_._. __<><
[___||.__|__/|__||\/|: Information Retrieval, System Integration
___|||__||..\|..||..|: Contact
AndrzejBialecki to the ContributorsGroup. Thanks!
--
Best regards,
Andrzej Bialecki
http://www.sigram.com, blog http://www.sigram.com/blog
___.,___,___,___,_._. __<><
[___||.__|__/|__||\/|: Information Retrieval, System In
ks.
However, even this new tool will make a copy of the original index, so
you will need twice as much space. But in this case perhaps you could
put the original index on a network FS, and split it into the target
partition - the
ke/DocReconstructor.java
If you really need such kind of access in your application then add your
documents with term vectors with offsets and positions. Even then,
depending on the Analyzer you used, the process is lossy - some input
data that was discarded by Analyzer is simply no longer available
Is there an alternative way to do
> that?
Yes, see the discussion here:
https://issues.apache.org/jira/browse/LUCENE-2393
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic W
On 2010-05-31 10:54, Uwe Schindler wrote:
> No.
See also LUCENE-2048 (nice round number ;) ).
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | E
it doesn't rely on this behavior. You
have been warned :)
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://ww
tent can be recovered. See the "Reconstruct &
Edit" functionality in Luke (http://www.getopt.org/luke).
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__
recorded in the
output index.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contac
On 2010-07-07 14:49, Naveen Kumar wrote:
Hi Andrzej Bialecki
When you suggested -
"There are some other low-level ways to do this, but the easiest is to
use a FilterIndexReader, especially since you just want to add a
stored
field - implement a subclass of FilterIndexR
->DF map with values obtained from the full index, and then you use
this map to calculate IDF.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedd
ributing bug reports, patches and comments.
Happy Luke-ing!
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www
ectly using IndexReader.setNorm(...) but
you need to remember that this method uses raw byte values, that is the
result of encoding a floating point value with
Similarity.encodeNormValue(..).
--
Best regards,
Andrzej Bia
more details:
http://people.ischool.berkeley.edu/~hearst/research/tilebars.html
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www
Hi all,
Luke 3.3.0 has been released and is available for download here:
http://code.google.com/p/luke/
Apart from the updated Lucene libraries there were no changes in
functionality.
--
Best regards,
Andrzej Bialecki
APIs.
* Rearranged "field flags" so that they are more logical and cover
index options added in 3.4.0. E.g. omitNorms is represented as
"with Norms" and marked by "N", IndexOptions are expanded to "Idfp"
to mark indexed fields with docs, freqs and
some
lesson to learn from this situation...
I committed a fix, and the updated release is marked as 3.4.0_1. Sorry!
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval
find a ranked list of documents that have the smallest
bit-level distance in their hashes from the query hash.
The solution is described in SOLR-1918 - Bit-wise scoring field type.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ _
On 31/10/2011 21:42, Petite Abeille wrote:
On Oct 31, 2011, at 9:32 PM, Andrzej Bialecki wrote:
similarity-preserving hash function was calculated on each sentence, and the
hash was added as a field. The property of the hash was that similar documents
(sentences) would produce a similar
ts only omitNorms. So the flags are set now like this:
isIndexed = true;
isTokenized = true;
omitNorms = true;
The end result of processing such a field is (I believe) conceptually
equivalent to adding as many Fields as there are tokens, each with
omitNorms=true.
--
Best
Otis Gospodnetic wrote:
So in other words, it *is* possible to have the field both tokenized and its
norms omitted?
Yes. Probably this is an unintended side-effect of adding setOmitNorms,
but I think it's useful and IMHO we should keep it.
--
Best regards,
Andrzej Bia
or each "1".)
We are discussing the same thing in "Case sensitivity" thread - it's
possible to have a tokenized field and omit its norms.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[_
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at
one during scoring and not afterwards. FilteredQuery internally
makes use of skipTo(), which should help to limit the number of
evaluated docs.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retr
Grant Ingersoll wrote:
On Aug 30, 2008, at 3:14 PM, Andrzej Bialecki wrote:
I think you can use a FilteredQuery in a BooleanClause. This may be
faster than the filtering code in the Searcher, because the evaluation
is done during scoring and not afterwards. FilteredQuery internally makes
: ConjunctionScorer, lines 85-103 - pay attention to the
comments there, it's not strictly a sort by frequency, rather by the
sampled "sparseness".
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/
vide static methods on Fieldable that test the
validity of flag combinations with particular version of Lucene?
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \|
n it won't cause any IO,
otherwise it needs to read this info from the .ti file.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System
index to a new format, incompatible with earlier versions of
Lucene (including 2.4 release).
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded
Andrzej Bialecki wrote:
1) Luke 2.4 release. This has the advantage of being an official stable
[...]
2) Luke 2.9-dev snapshot. This has the advantage that you get the
[...]
Of course I meant Lucene 2.4 and Lucene 2.9-dev ... sorry for the confusion.
--
Best regards,
Andrzej Bialecki
ss someone else does it it's simply not going to
happen. All code in Luke except for the Thinlet class is under Apache
License, so feel free to start coding :)
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/
- we can include this in the proposals for the next
summer.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http:
ntent of these deleted documents, call first
IndexReader.undeleteAll().
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
htt
, although I tested all functionality to make sure that there is
no data loss.
HOWEVER, if you work with precious data, it's always a good idea to use
the "Read-only" option.
As usually, bug reports or suggestions for improvements, or even better
patches, are welcome!
but in practice Luke directly accesses
the underlying Directory in many other places ... I forgot about the use
of IndexFileDeleter - and indeed passing the read-only flag here can
solve this, because then I can always use KeepAllDeletionPolicy when
opening read-
. (with a score etc)
I can see the case for this would be a news-article and several people
writing queries to get alerted if it matched a certain condition.
http://www.seas.upenn.edu/~svilen/publications/subscribe.pdf
--
Best regards,
Andrzej Bialecki
ll commits" option was specified. Reported by Mark Harwood.
o Empty index with no fields was reported as invalid. Discovered by
Andrew Zhang and Michael McCandless (LUCENE-1454).
Thank you!
--
Best regards,
A
n turn _require_
the presence of a common-grams.utf8 resource on the classpath.
To summarize: unless you want to get your hands dirty with Luke
internals it can't be done.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
g 2.4 , the
search worked fine using 2.4.
Any ideas why this is happening.
No idea - but perhaps this is somehow related:
https://issues.apache.org/jira/browse/LUCENE-1452
--
Best regards,
Andrzej Bia
versions of Lucene involved.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: inf
formation this
way would be messy - it's better to propose that this information should
be added to API.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| |
Hi all,
I apologize for the inconvenience - the site went down without any prior
notice from the ISP. I'm investigating the issue ...
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval
liat oren wrote:
Ok, thanks.
I will have to edit the code of Luke in order to add another analyzer,
right?
No - if your analyzer is already on the classpath, then it's enough to
type in the fully qualified class name in the drop down box (it's editable).
--
Best regards,
Andrze
the classpath when you start Luke.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info
plement an arbitrary re-sorting of top-N
results, according to your rules of preference (business rules, or
heuristics). This way you can avoid the overfitting or doing endless
tweaking, and still get the ranking that makes sense to your users.
--
Best regards,
Andrze
ounts per field in Overview - contributed
by Mark Harwood.
o Improved the Analysis plugin to show all token information,
and highlight whenever a token is selected from the list.
* Bug fixes:
o (None)
--
Best regards,
Andrzej Bia
Andrzej Bialecki wrote:
(sorry for cross-posting)
Hi all,
I'm happy to announce a new release of Luke, the Lucene Index Toolbox.
As usually, you can obtain it from here:
http://www.getopt.org/luke
If you tried to access this url during last couple hours the site was
down. It s
.
* repeat the cycle as many times as needed
A more elegant version of this algorithm can be implemented using
FilterIndexReader.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retr
space.
(Actually: does CheckIndex warn about unused files in the index directory
so people can clean them up? i'm not sure)
It doesn't. But Luke has a function to do this.
--
Best regards,
A
(http://www.getopt.org/luke) can
export all stored fields from all documents into an XML file.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, Syst
rg/jira/browse/LUCENE-532
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.co
welcome - please keep in mind that this is an early
preview. Also, various UI glitches are probably related to the Thinlet
toolkit - again, one day I may re-write Luke using something else, but
for now I don't have the strength to do it.
atch to Andrzej, the author of Luke.
Thank you Phil for spotting this bug - this fix will be included in the
next release of Luke.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Sem
nized" version of the field. At this point any potential mismatch
in query terms vs. analyzed tokens in the field should become apparent.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Se
rsday, September 3rd 2009
11:00-11:30AM PDT / 14:00-14:30 EDT
Follow this link to sign up:
http://www2.eventsvc.com/lucidimagination/event/ff97623d-3fd5-43ba-a69d-650dcb1d6bbc?trk=WR-SEP2009-AP
About:
Lucene Performance Workshop:
Understanding Lucene Search Performance
with Andrzej Bialecki
Experi
e-for-Lucene
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at
Chris Pimlott and
others.
Enjoy! :)
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.co
Andrzej Bialecki wrote:
Hi all,
I'm happy to announce the new release of Luke - the Lucene Index Toolbox.
There's a bug in this version in that it doesn't show TermVectors for a
field. I'll fix it in a few days - I'm waiting for other potential bugs
to show up. So i
while) that if the terms
you load are indexed that'll help. But this is mostly
a guess.
Just to clarify: IndexReader.document(doc) and .document(doc, selector)
load _only_ stored fields, they don't interact at all with the
terms-related part of Lucene..
--
Best
yourself ;) Keyboard shortcuts are hardcoded somewhere deep in Thinlet,
but likely they could be made configurable.
You can find an EPS version of the Lucene logo here:
http://lucene.apache.org/images/logo.eps
d you can
even create other fields in the document (or split this token stream
into several fields).
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| ||
ability to edit per-commit user data Map
Bug fixes
-
* Term frequency vectors were not displayed for selected field.
Enjoy!
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retr
that this encoding causes
(and what input values effectively come out the same, once encoded).
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Em
tween Lucene 2.9.1 and 3.0.
Your feedback is welcome - please use the Google Issue tracker to report
issues.
Merry Christmas!
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval
existent fall back to the zero-arg ctor.
>
> I'll open an issue.
Indeed - thanks!
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix
t your own Fieldable, and return what you want
from its methods. You can also use Field constructor that takes the
stored value, and then use Field.setTokenStream(TokenStream) - it
doesn't override the stored value.
--
Best regards,
A
merge segments).
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact
this parser out of the box. I
expect to make a release within a few days. Watch the commits on the
Google code project ...
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval
gards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at
textarea.
I'll commit the current mostly-working state today, you can take a look
- you've written some cool Luke plugins before .. ;)
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Informa
ally one could store such information in
IndexCommit.getUserData(). The lack of standardized metadata is an
issue, of course - we could start experimenting with this in Luke, to
see whether we can squeeze a subset of Solr schema there.
--
Best
lyzer plugin (and analyzers) don't work.
* Issue 4 : Compress flag no longer available.
* Issue 14 : Error while using custom similarity.
Enjoy!
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information
trouble ;)
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigr
luable enough to do ...
Alternatively, we could just take this code and add it to
IndexReader.renameField(String old, String new) ... ;)
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Informat
[EMAIL PROTECTED] wrote:
Dear Andrzej Bialecki
Can we change the field name in *.fnm directly by hand?
Yes, but you need to be consistent about it, i.e. change it the same way
for every segment that the index consists of. Also, fnm files are binary
files, so you need to know the format
l large-ish bins, and apply arbitrary sorting
methods within each bin. Studies show that if you pick the right bin
size, users will rarely look into the second and the following bins, so
the task is reduced to the sorting of the first bin, e.g. 100 top
scoring docs.
--
Best regards,
Andrz
a function of the current index format - perhaps in the
future Lucene will be able to store these values separately using
another type of storage. So far there was no pressing need to do this).
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _
rrect?
(I'm not involved in Wikia development). There are some ways to go about
it even in the pure Lucene-land, so that the updates are fast without
reindexing the main content. Hint: ParallelReader.
--
Best regards,
Andrze
Ryan McKinley wrote:
Andrzej Bialecki wrote:
Lukas Vlcek wrote:
So staring will be accommodated only during indexing phase. Does it
mean it
will be pretty static value not a dynamically changing variable...
correct?
In other words if I add my starts to some document it won't affec
simple
to implement, yet produces useful results difficult to obtain through
the usual means (similarity, boosting, even function query).
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retr
local filesystem first...
Yes - see org.apache.nutch.indexer.FsDirectory. However, you will not
like the performance, it's much slower than using the index locally.
--
Best regards,
Andrzej Bia
ynced to the on-disk index), and start using
the new IndexSearcher.
And again, start accumulating new docs in the RAMDirectory, etc, etc ...
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information
://wt.jrc.it/lt/Acquis/
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigra
g more relevant.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact
emented (yet?).
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.co
lass applicable to various scenarios.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System In
m an index. Instead
this column now reads "Norms" and shows the fieldNorm value of a field.
Have fun!
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__||
1 - 100 of 202 matches
Mail list logo