Hi Rafaela,
I built something along these lines as a proof of concept. All data in the
index was unstored and only fields which were searchable (tokenized and
indexed) were kept in the index. The full record was encrypted and stored in a
MongoDB database. A custom Solr component did the search
Thanks!
Sriram.
On Tue, Jun 25, 2013 at 10:01 AM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> On Tue, Jun 25, 2013 at 12:49 PM, Sriram Sankar wrote:
> > I have a use case where I build my index only occasionally and am willing
> > to pay the cost to build a read-only index that oc
On Tue, Jun 25, 2013 at 12:49 PM, Sriram Sankar wrote:
> I have a use case where I build my index only occasionally and am willing
> to pay the cost to build a read-only index that occupies as small a memory
> footprint as possible and also remains efficient for posting list
> traversal. I.e., I
I have a use case where I build my index only occasionally and am willing
to pay the cost to build a read-only index that occupies as small a memory
footprint as possible and also remains efficient for posting list
traversal. I.e., I will not be making any changes at all once it is built.
1. Wha
It depends on which version of Lucene you are using. With Lucene 4,
TermAttribute has been replaced with CharTermAttribute. I believe
TermAttribute was simply deprecated in Lucene 3.
Cheers,
Ivan
On Mon, Jun 24, 2013 at 11:32 PM, 雨与泪 <1137925...@qq.com> wrote:
> I can't find the Class of TermAt
I can't find the Class of TermAttriubte,which has the way of term.so I can't do
it work.how to set encoder to the class(termAttribute)
On Tue, Jun 25, 2013 at 1:03 PM, Rafaela Voiculescu
wrote:
> Hello,
Hi,
> I am sorry I was not a bit more explicit. I am trying to find an acceptable
> way to encrypt the data to prevent any access of it in any way unless the
> person who is trying to access it knows how to decrypt it. As I ment
Hello,
Thank you for the answers.
I am sorry I was not a bit more explicit. I am trying to find an acceptable
way to encrypt the data to prevent any access of it in any way unless the
person who is trying to access it knows how to decrypt it. As I mentioned,
I looked a bit through the patch, but
Hi,
On Mon, Jun 24, 2013 at 6:13 PM, Mathias Lux wrote:
> When searching for an image within memory I came down to 44ms.
> Therefore, 77ms is totally acceptable in these terms. My benchmarking
> of the BinaryDocValuesField showed that it'd come close to the 44ms,
> but I didn't go for a full eval
