solr - ignore fields

Hello 1) Is it possible to specify fields to be ignored when a document is indexed (perhaps via an annotation)? 2) Are all fields added to an index? I could use 'skip' to ensure that a field is not indexed but would prefer the field to be igonored? 3) How can I view '_rs_schema' via http

Re: About Protocol Buffers

Alex, There's a mistake in that tutorial that I need to fix. Early in the tutorial I instruct you to create a bucket type called *counters*, and then later on I use the name *counter_bucket*. Silly mistake on my part. If you establish that as the bucket type, it should work: *bucket = client.buck

Re: About Protocol Buffers

Hi Luc, I tried your new solution and gives the same error. The problem is that .bucket_type() doesn't exist: Traceback (most recent call last): File "test.py", line 18, in bucket = client.bucket_type('counters').bucket('likes') AttributeError: 'RiakClient' object has no attribute 'bucket_

AAE Alredy held by process

Riak cluster 7 nodes, 1.3.2 Sometime riak node crashes and not responde at all. On one node: 2014-06-24 14:29:56 =ERROR REPORT Error in process <0.8303.2> on node 'riak@de3' with exit value: {badarg,[{erlang,binary_to_term,[<<19047 bytes>>],[]},{hashtree,get_disk_bucket,3,[{file,"src/ha

Re: About Protocol Buffers

Alex, Not all Riak 2.0 features have been merged to master on the Python client, including CRDTs. We are in final testing of that feature and will have a release candidate package of the client out soon. On Tue, Jun 24, 2014 at 5:26 AM, Alex De la rosa wrote: > Hi Luc, > > I tried your new sol

Re: About Protocol Buffers

Sean, Thank you very much for your answer; somehow I imagined the Python library may not be updated with last code. Can't wait to be out as I can not fully test everything I need for my project. Thanks, Alex On Tue, Jun 24, 2014 at 3:35 PM, Sean Cribbs wrote: > Alex, > > Not all Riak 2.0 feat

1.4.8, memory_backend max_memory not honored?

Test cluster with 2 machines running 1.4.8 with the memory backend. app_config has ring_creation_size 64, max_memory 4. If I understand the documentation correctly this should result in a maximum memory footprint (minus overhead) of 256M. Each node has 2G RAM, 2G of swap. After running for a

Re: 1.4.8, memory_backend max_memory not honored?

Hi Allen, There were some fixes to the memory backend in 1.4.9: https://github.com/basho/riak/blob/1.4/RELEASE-NOTES.md Could you please provide your app.config file? I'd like to check it and test out your scenario locally. -- Luke Bakken CSE lbak...@basho.com On Tue, Jun 24, 2014 at 8:59 AM,

Re: 1.4.8, memory_backend max_memory not honored?

Sure Luke. The app.config is attached. Does that riak_kv/940 sound like it could be responsible? On 6/24/2014 12:15, Luke Bakken wrote: Hi Allen, There were some fixes to the memory backend in 1.4.9: https://github.com/basho/riak/blob/1.4/RELEASE-NOTES.md Could you please provide your app.co

Re: 1.4.8, memory_backend max_memory not honored?

Hi Allen, Apart from the memory backend, AAE will also be consuming memory as you currently have it enabled. I would recommend running the test again with anti entropy turned off to see how much impact that has. Best regards, Christian On Tue, Jun 24, 2014 at 5:29 PM, Allen Landsidel wrote

Re: 1.4.8, memory_backend max_memory not honored?

Thanks Christian, Giving that a try while I build a new 1.4.9 test cluster. On 6/24/2014 13:27, Christian Dahlqvist wrote: Hi Allen, Apart from the memory backend, AAE will also be consuming memory as you currently have it enabled. I would recommend running the test again with anti entropy tur