In a recent post, someone asked about storing "metadata" in a document. My guess would have been to use add_value. Olly's recommendation was to use set_data. What are the general guidelines for deciding whether to use values or data in a document? Garrett
Garrett Smith wrote on 1/1/10 7:31 AM: > In a recent post, someone asked about storing "metadata" in a > document. My guess would have been to use add_value. Olly's > recommendation was to use set_data. > > What are the general guidelines for deciding whether to use values or > data in a document? > values can be used for sorting and filtering results. data is arbitrary storage associated with a document. where you store your metadata depends on how you intend to use it. -- -- Peter Karman . http://peknet.com/ . peter <at> peknet.com
On Fri, Jan 1, 2010 at 8:15 AM, Peter Karman <peter <at> peknet.com> wrote: > Garrett Smith wrote on 1/1/10 7:31 AM: >> >> In a recent post, someone asked about storing "metadata" in a >> document. My guess would have been to use add_value. Olly's >> recommendation was to use set_data. >> >> What are the general guidelines for deciding whether to use values or >> data in a document? >> > > values can be used for sorting and filtering results. > data is arbitrary storage associated with a document. > > where you store your metadata depends on how you intend to use it. Thanks Peter. Is there any additional cost in storing values rather than data? It seems far more convenient to store "metadata" type information in values rather than data given they can be retrieved individually. I.e. using data, one has to encode/decode a single opaque value so I'm assuming there's some payoff in that case (index size, indexing performance, etc.)
> Is there a way to get a list of spelling suggestions from Xapian? > Database::get_spelling_suggestion (obviously) returns just a single > suggestion. Call get_spelling_suggestion for each word in your query. Some assembly required ;)
2010/1/5 <henka <at> cityweb.co.za>: >> Is there a way to get a list of spelling suggestions from Xapian? >> Database::get_spelling_suggestion (obviously) returns just a single >> suggestion. > > Call get_spelling_suggestion for each word in your query. > > Some assembly required ;) That's not quite the same thing, though: it would be nice to be able to get more than one suggestion even for a single word. To answer the question - no, there's currently no way to get multiple suggestions from Xapian. It would be a good thing to add, though, I think. -- -- Richard
Hi all, We are organising another open source search social evening (OSSSE?) in London on Tuesday the 12th of January. The plan is to get together and chat about search technology, from Lucene to Solr, Hadoop, Mahout, Xapian, Ferret and the like - bringing together people from across the field to discuss ideas and ask questions over a quiet drink. We've also created a group on Meetup.com where you can sign up to get notifications by email about upcoming search socials. For directions to this meetup and for the Meetup.com group see: http://www.meetup.com/london-search-social/ Please come along if you can! René & Rich (Marr) _______________________________________________ Xapian-discuss mailing list Xapian-discuss <at> lists.xapian.org http://lists.xapian.org/mailman/listinfo/xapian-discuss
> 2010/1/5 <henka <at> cityweb.co.za>: >>> Is there a way to get a list of spelling suggestions from Xapian? >>> Database::get_spelling_suggestion (obviously) returns just a single >>> suggestion. >> >> Call get_spelling_suggestion for each word in your query. >> >> Some assembly required ;) > > That's not quite the same thing, though: it would be nice to be able > to get more than one suggestion even for a single word. Oops, sorry - my eyes skimmed over the important "returns ... a single suggestion." bit.
g' day Configured with --disable-maintainer-mode. Compilation of revision 13824 is failing with: common/serialise-double.cc: In function double unserialise_double(const char**, const char*): common/serialise-double.cc:141: error: SerialisationError is not a member of Xapian common/serialise-double.cc:157: error: SerialisationError is not a member of Xapian common/serialise-double.cc:169: error: SerialisationError is not a member of Xapian Regards Henry
2010/1/13 <henka <at> cityweb.co.za>: > g' day > > Configured with --disable-maintainer-mode. I suspect that's your problem. SerialiseDouble is defined in include/xapian/error.h This is a generated file, but if you're using --disable-maintainer-mode the rules to generate the file aren't included. The compilation must be finding a version of xapian/error.h somewhere. My first guess would be that it's finding a copy from a system installed version of Xapian which is old enough not to include SerialiseDouble. Failing that, I'd guess that you've copied some files in from somewhere other than SVN, or had some lying around when you updated your checkout. To fix, configure with --enable-maintainer-mode (you may want to use --disable-documentation, to reduce the number of dependencies you need to install. Alternatively, just build from a snapshot tarball: http://oligarchy.co.uk/xapian/trunk/ -- -- Richard
RSS Feed2 | |
|---|---|
35 | |
22 | |
67 | |
86 | |
49 | |
52 | |
55 | |
53 | |
40 | |
58 | |
43 | |
28 | |
50 | |
45 | |
33 | |
63 | |
64 | |
50 | |
34 | |
67 | |
21 | |
41 | |
54 | |
58 | |
73 | |
50 | |
97 | |
63 | |
150 | |
72 | |
94 | |
83 | |
119 | |
109 | |
116 | |
92 | |
68 | |
114 | |
161 | |
117 | |
92 | |
97 | |
92 | |
55 | |
62 | |
130 | |
104 | |
95 | |
191 | |
84 | |
155 | |
186 | |
143 | |
147 | |
137 | |
213 | |
180 | |
150 | |
128 | |
174 | |
96 | |
142 | |
220 | |
101 | |
88 | |
116 | |
88 | |
98 | |
154 | |
136 | |
229 | |
196 | |
123 | |
75 | |
38 | |
61 | |
80 | |
78 | |
29 | |
78 | |
59 | |
44 | |
79 | |
37 | |
33 | |
78 | |
34 | |
108 | |
141 | |
49 | |
34 | |
107 | |
112 | |
45 | |
202 | |
47 | |
63 | |
39 | |
8 | |
28 | |
40 | |
16 | |
66 | |
19 | |
41 | |
43 | |
22 | |
15 | |
14 | |
20 |
