Re: [riak-user]Cannot startup riak node correctly after successful installation

YouBarco writes: > Hello, > > My OS is ubuntu 14.04 64bit, and installed erlang from source with version > R16B as following: That's your problem. You MUST use the custom Basho branch of Erlang/OTP with Riak. If you insist on building Erlang/Riak from source then follow this guide for Erlang:

Re: risk attach not working properly after operation

Oliver Soell writes: > That was all well and good, but now “riak attach” isn’t giving me the love I > thought I should get: > > (c_1494_riak@172.29.18.183)1> {ok, Ring} = > riak_core_ring_manager:get_my_ring(). > ** exception error: no match of right hand side value {error,no_ring} > (c_1494_ri

Re: Yokozuna - inconsistent number of documents found for the same query

Eric Redmond writes: > This is a known issue, and we're still working on a fix. > > https://github.com/basho/yokozuna/issues/426 > I don't see how this issue is related to Oleksiy's problem. There is no mention of removing or adding nodes. I think the key part of Oleksiy's report is the associat

Re: Yokozuna error during indexing

Oleksiy Krivoshey writes: > Got few results: > > I don't see anything wrong with the first record, but the second record > mentions the key '/.Trash/MT03' which is not correct, the correct key that > exists in that bucket is > > '/.Trash/MT03 348 plat frames' > You have found a bug in Yokozuna.

Re: Yokozuna error during indexing

Oleksiy Krivoshey writes: > > Entropy Trees > > Index Built (ago) > --- > 114179815416476790484662877555959610

Re: Yokozuna error during indexing

Oleksiy Krivoshey writes: > > Still, what kind of base64 string can it be? I don't have anything base64 > encoded in my data, its a pure JSON objects stored with content_type: > 'application/json' The _yz_* fields (which need to be part of your schema and defined exactly as defined in the defaul

Re: Yokozuna error during indexing

Oleksiy Krivoshey writes: > Yes, I'm using custom schema and custom bucket type. There are many (over > 500) buckets of this type. Did you modify any of the _yz_* fields? > Your command have returned the following tuple: > > (riak@10.0.1.1)1> redbug:start("yz_solr:to_pair -> return"). > {1919,1

Re: Yokozuna error during indexing

Oleksiy Krivoshey writes: > Hi, > > I have enabled Yokozuna on existing Riak 2.0 buckets and while it is still > indexing everything I've already received about 50 errors like this: > > emulator Error in process <0.26807.79> on node 'riak@10.0.1.1' with exit > value: > {{badmatch,false},[{base64,

Re: Solution for Riak 500 Internal Server Error

On Oct 14, 2014, at 3:53 AM, ayush mishra wrote: > http://www.dzone.com/links/r/solution_for_riak_500_internal_server_error.html > ___ > I recommend _not_ using legacy Riak Search on Riak 2.x. Why was the legacy search pre-commit hook installed in

Re: Yokozuna Scale

On Sep 18, 2014, at 10:35 AM, anandm wrote: > Yes Ryan - that aspect is pretty clear. So with 1-1 riak-solr Yokozuna > deployment scale to my requirement? Am I missing something here when > thinking it wouldn't? I haven’t followed this thread closely, it was just your last email that caught my

Re: Yokozuna Scale

On Sep 18, 2014, at 4:20 AM, anandm wrote: > Yes - looks like its going that way too - a decoupling between the Solr Cloud > and the Riak Cluster seems like a solution that could work out and then > Yokozuna to index content out to the Solr Cloud (completely external to riak > - Solr not made to

Re: Optimistic Locking with Riak Search / is _version_ required in schema.xml?

On Aug 7, 2014, at 5:46 PM, David James wrote: > Is _version_ required? It should not be required as the documentation says it is only needed for real-time GET which Riak Search (Yokozuna) disables since Riak KV provides the get/put implementation. > I see SolrCloud mentioned in some document

Re: Riak Search 2.0 Questions

On Jul 24, 2014, at 12:29 PM, Andrew Zeneski wrote: > Been checking out 2.0rc1 and am really excited about the new features (as I > think most of us are). I had a couple of questions that I couldn't find > answers to scanning the docs. Totally possible I missed it and if so, please > feel fre

Re: Yokozuna search

On Jul 23, 2014, at 10:02 AM, Sean Cribbs wrote: > . In this case, no, you cannot use wildcards at the beginning [1]. > [1] http://lucene.apache.org/core/2_9_4/queryparsersyntax.html#Wildcard > Searches > Actually, you can place the wildcards * or ? anywhere, it doesn’t matter. When placin

Re: Endless AAE keys repairing

On Jul 17, 2014, at 4:30 AM, Daniil Churikov wrote: > Hello, In our test env we have 3 nodes riak 1.4.8-1 cluster on debians. > According to logs: 2014-07-17 02:48:03.748 [info] > <0.10542.85>@riak_kv_exchange_fsm:key_exchange:206 Repaired 1 keys during > active anti-entropy exchange of > {9

Re: AAE problems

On Tue, Jun 17, 2014 at 12:46 PM, István wrote: > > > The entire dataset is idempotent and immutable, so there is not even a > slightest chance that we are ending up with different values on > different nodes for the same key in the same bucket. It seems that > anti-entropy still finds problems: >

Re: Search sort error in 2.0.0beta1

This seems like a bug to me. I created an issue to track it. https://github.com/basho/yokozuna/issues/372 On Thu, May 1, 2014 at 5:22 PM, Troy Melhase wrote: > Hello again! > > I've narrowed this down to the interaction between the sort parameter and > the field list ("fl") parameter. It see

Re: how to set eDisMax? Solr start and rows not working properly

On Sun, Apr 20, 2014 at 9:57 AM, Buri Arslon wrote: > Hi guys! > > I searched the docs and the source code but wasn't able to find any info > about using edismax. > > I have 2 questions: > > 1. How to set edismax parser? > You can make use of LocalParams syntax in order to use different query pa

Re: Riak 2.0 search changes

Alexander, > 1. Does it support wildcards in a middle or start? *abc, a*bc, Riak Search 2.0 (Yokozuna) is based on Apache Solr. Any queries supported by Solr's distributed search are supported by Search 2.0 over HTTP. The PB API has not been altered for Search 2.0 (with the exception of presort)

Re: Riak search fails to index via riakc_pb client

> > Index via the erlang client (error) > > === > > Eshell V5.9.2 (abort with ^G) > 1> {ok, Conn} = riakc_pb_socket:start_link("localhost", 8087). > {ok,<0.34.0>} > 2> Body = <<"{\"name_s\":\"tom\"}">>. > <<"{\"name_s\":\"tom\"}">> > 3> Object2Store = > riakc_obj:

Re: updating the default bucket-type to support Solr indexing?

There is support for indexing CRDTs. Field definitions are defined in the default schema: https://github.com/basho/yokozuna/blob/develop/priv/default_schema.xml#L96 On Mon, Mar 24, 2014 at 12:33 PM, Paul Walk wrote: > Thanks Luke. > > If I might be allowed a follow-on question, what is the eff

Re: updating the default bucket-type to support Solr indexing?

Actually, a bucket type is not required. To associate an index with a bucket you simply set the `search_index` property. Bucket types provide a method for many buckets to inherit the same properties. Setting the search_index property on the bucket type is a way to index multiple buckets under one i

Re: Riak 2.0 Yokozuna performance

On Wed, Mar 19, 2014 at 4:15 AM, Andrey Anpilogov wrote: > Hi, > > I've been playing with Riak 2.0 and found some strange performance drop > with new Search system. > Run two Riak nodes on E3 machines with 32GB RAM and SSD drives. > 1) Use leveldb as backend. > 2) Enabled Search engine > 3) Join

Re: Search Index Not Found

On Sat, Mar 22, 2014 at 2:57 PM, Buri Arslon wrote: > another weird thing I noticed is that after I restart riak, > get_search_index returns {ok, Index}, but after a few seconds, it's going > back to {error, "notfound"} > > Do you see any errors related to that index in the solr.log file? ___

Re: How to disassociate a bucket with a yokozuna index?

On Tue, Mar 11, 2014 at 4:17 AM, EmiNarcissus wrote: > > Now I'm working with riak 2.0 pre17, have tried both set bucket property > search_index to other index or _dont_index_, but still cannot delete the > index. > > > Failure: riakasaurus.exceptions.RiakPBCException: Can't delete index with > as

Re: How to disassociate a bucket with a yokozuna index?

On Sun, Mar 9, 2014 at 8:31 AM, EmiNarcissus wrote: > > I'm testing on yokozuna api now, but found every time I call > delete_search_index function it alerts cannot delete because of pre-existed > associated bucket. I've tried to set the bucket search-index to another > index, still have the same

Re: [ANN] Yokozuna 0.14.0

/riak-yokozuna-0.14.0-src.tar.gz.sha1 The latest install doc has the corrected links. https://github.com/basho/yokozuna/blob/develop/docs/INSTALL.md#source-package -Z On Mon, Feb 24, 2014 at 12:36 PM, Ryan Zezeski wrote: > Riak Users, > > I'm happy to announce the Yokozuna 0.14

[ANN] Yokozuna 0.14.0

Riak Users, I'm happy to announce the Yokozuna 0.14.0 release. It brings an upgrade to Solr 4.6.1 as well as a slew of bug fixes and internal enhancements. There are breaking changes made in this release so if you are one of the brave souls using riak2.0.0 pre5/pre11 or a previous Yokozuna source

Re: yokozuna Issues

Hello Bryce, On Wed, Feb 19, 2014 at 3:27 PM, Bryce Verdier wrote: > Hey Hector, > > Thank you for looking into this, here is the response to 'java -version' > on my machine: > java -version > java version "1.7.0_51" > OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31) > OpenJDK 64-

Re: riak crashing when indexing for search

Hi Glory, On Tue, Feb 11, 2014 at 1:29 AM, Glory Lo wrote: > > > While indexing it seem to run fine part way.. then I noticed it hangs (it > freezed my machine on a couple of attempts on linux mint 13). Then it > crashes. I have 3 nodes running and I only tried indexing one of them > doing a se

Re: Yokozuna and array of JSON documents

Hi Srdjan, On Mon, Feb 3, 2014 at 12:06 PM, Srdjan Pejic wrote: > > > [{"viewer_id_s"=>"004615eb-5c0e-4c4a-890c-c6fc29e3fc56", >> "video_time_i"=>475, "type_s"=>"joined"}, >> {"viewer_id_s"=>"635dcd2d-fdeb-46c1-9920-803ccdd6176b", >> "video_time_i"=>522, "type_s"=>"joined"}, >> {"viewer_id_s"=>"

Re: Search schemas in 2.0pre11

On Tue, Feb 4, 2014 at 4:38 PM, Jeremy Pierre wrote: > Hi Eric, > > Thanks very much - getting a 405 response for that curl command though. > POST to same endpoint yields the following: > > The schema resources does not accept POST requests. Only PUT and GET. -Z

Re: Timeouts on Riak Search

On Mon, Jan 27, 2014 at 5:20 PM, Ryan Zezeski wrote: > > > I see you are doing a disjunction search across the type field `(type:image > type:video type:FacebookPost)`. How many documents match that sub-query? > If it is over 100k then legacy Riak Search will fail to retu

Re: Timeouts on Riak Search

On Sun, Jan 26, 2014 at 7:41 PM, ender wrote: > I am continuously getting the following types of errors in my riak logs: > > 2014-01-27 00:06:39.735 [error] <0.220.0> Supervisor riak_pipe_builder_sup > had child undefined started with {riak_pipe_builder,start_link,undefined} > at <0.18590.125> ex

Re: Riak Search and Yokozuna Backup Strategy

On Mon, Jan 27, 2014 at 4:02 PM, Elias Levy wrote: > > > So it would appear to do it properly, we'd need some support from Yokozuna > to take the snapshot, return a list of files to backup or back them up > itself (hard links?), and then to allow an application to signal it to > release the snapsho

Re: Riak Search and Yokozuna Backup Strategy

Hi Elias, On Mon, Jan 27, 2014 at 2:40 PM, Elias Levy wrote: > > > Any comments on the backup strategy for Yokozuna? Will it make use of > Solr's Replication Handler, or something more lower level? Will the node > need to be offline to backup it up? > There is no use of any Solr replication c

Re: Split index with Riak 2.0 git (jan 15th) on a single dev node cluster

John, 1. What did you use to load the data? Do you have a script? 2. What content-type is the data? 3. Do you see any errors in the log directory? Check error.log and solr.log. 4. Do you get any results for the query q=_yz_err:1 5. Did you wait at least 1 second before running the queries? 6.

[ANN] Yokozuna 0.13.0

Riak Users, It was a little late due to the holidays but Yokozuna 0.13.0 is here. This release brings an upgrade to Solr, support for indexing Riak Data Structures, the ability to reload indexes via `riak attach`, and includes a query performance boost. See the release notes for more details. htt

Re: Cluster restarted and doesn’t respond to queries

On Mon, Dec 23, 2013 at 12:35 PM, Justin Lambert wrote: > > I do see some errors in the error.log, but the referenced directories > don’t appear to exist: > 2013-12-23 16:52:33.290 [error] > <0.1721.0>@riak_kv_bitcask_backend:move_unused_dirs:607 Failed to move > unused data directory > "./data/le

[ANN] Yokozuna 0.12.0

Riak Users, I'm happy to announce the Yokozuna 0.12.0 release today. This release integrates the new bucket type feature and adds the ability to migrate from Riak Search using AAE. Less disk space will be used per index and a slight bump in query performance may be noticed. Also, documentation wa

Re: badrecord during transfer

Ivan, What makes you think the index is damaged? From what I can see this is a bug in the code assuming that a #ho_acc record is always returned but in fact an error tuple could also be returned. That error tuple could be caused by index corruption but there is nothing in your email to say for sur

Re: [Confusing search docs] Enabling search on bucket in Riak 2.0

o go > > Here is the data: > "[2013-11-27T15:21:30] [ERROR] [192.168.1.102] [zach.scratchd.ca] [0] [ > thakore.kar...@gmail.com] test" > > Here is the search: > http://192.168.1.10:8098/solr/logs/select?q=* > > http://192.168.1.10:8098/solr/logs/select?q

Re: [Confusing search docs] Enabling search on bucket in Riak 2.0

> I put in a text/plain entry with: > > > http://192.168.1.10:8098/riak/logs/26-11-2013T2260?vtag=47ffPuWSln7VhlTl02raJA > > [2013-11-26T22:43:26] [ERROR] [192.168.1.102] [0] [ > thakore.kar...@gmail.com] test > > > http://192.168.1.10:8098/riak/logs/26-11-2013T2260?v

Re: Search Crashes

On Wed, Nov 20, 2013 at 2:38 PM, Gabriel Littman wrote: > > > 1) We are installed via deb package > ii riak 1.4.1-1 > Riak is a distributed data store > There's a 1.4.2 out but your issue doesn't seem to have anything do with a specific 1.4.1 bug. > > 2) We did rec

Re: [Confusing search docs] Enabling search on bucket in Riak 2.0

On Wed, Nov 20, 2013 at 3:48 PM, Kartik Thakore wrote: > Thank you. > > I am creating indexes with: > > curl -i -XPUT http://192.168.1.10:8098/yz/index/allLogs \ >-H 'content-type: application/json' \ > -d '{"schema" : "_yz_default", "bucket" : "logs" }' > > > But when I check the i

Re: Search Crashes

Hi Gabriel, First, let me verify a few things. 1. You are on Riak 1.4? Which patch version? 1.4.2? 2. You recently upgraded you client? Did you have any of these failures before upgrading the client? 3. Have you made any other changes between the time your system was working and the time it sta

Re: Riak Search Map Reduce error

Roger, Riak Search has a hardcoded max result set size of 100K items. It enforces this to prevent blowing out memory and causing other issues. Riak Search definitely has some issues when it comes to handling a use case like yours. That said, our new Search solution in 2.0 (code named Yokozuna) sh

Re: Riak Yokozuna and a schema

Leif, I quickly wrote up a gist to show how you can use a custom schema with your index and associate it with multiple buckets. Be warned that the current version of Riak/Yokozuna uses bucket properties for storing the index association. These are stored in the ring and have a known limitation. Th

Re: [ANN] Yokozuna 0.11.0

at 9:29 AM, Ryan Zezeski wrote: > Riak Users, > > Today I'm happy to announce the 0.11.0 release of Yokozuna. > > This release brings Riak Java Client support as well as > authentication and security for the HTTP and protocol buffer > transports. An access control list (A

Re: Yokozuna Schema Changes

the new schema. > > Obviously a rolling restart of Riak isn't the biggest issue on earth, it's > not ideal either. > > --- > Jeremiah Peschka - Founder, Brent Ozar Unlimited > MCITP: SQL Server 2008, MVP > Cloudera Certified Developer for Apache Hadoop > >

Re: Yokozuna Schema Changes

Hi Jeremiah, Yes. I very much want the ability to update the schema in 2.0. More fundamental things have leap frogged it. Technically you can modify a schema today but it has to be done by hand and is error prone. -Z On Fri, Nov 8, 2013 at 6:42 PM, Jeremiah Peschka wrote: > I notice that YZ i

[ANN] Yokozuna 0.11.0

Riak Users, Today I'm happy to announce the 0.11.0 release of Yokozuna. This release brings Riak Java Client support as well as authentication and security for the HTTP and protocol buffer transports. An access control list (ACL) may be created to control administration and access to indexes. All

Re: riak search restore

Jon, The schema file is stored in a special bucket '_rs_schema' as well as cached in memory. -Z On Fri, Oct 4, 2013 at 2:33 AM, Jon Debonis wrote: > Hello, > > Riak includes these commands: > > search-cmd set-schema [INDEX] SCHEMAFILE > search-cmd show-schema [INDEX] > > Once imported

Re: Yokozuna: Riak Python client PB error with Solr stored boolean fields

Dave, This is a bug in Yokozuna. I have a hot-patch you can try. I'll email you directly with an attachment. I created an issue as well. https://github.com/basho/yokozuna/issues/209 -Z On Mon, Oct 14, 2013 at 9:27 PM, Dave Martorana wrote: > I studied the problem I was having with using

[ANN] Yokozuna 0.10.0

Riak Users, The 0.10.0 release of Yokozuna is ready. This release brings a few features such as an upgrade in Solr version along with some basic indexing and query stats. The default index has been removed returning write performance closer to baseline for non-indexed buckets. Disk usage was decr

[ANN] Yokozuna 0.9.0

Riak Users, The ninth release of Yokozuna has arrived. It is now integrated with the Riak development branch. This means no more special merge branches and you get the latest and greatest Riak code. It also means Yokozuna is on track to be delivered with the next release of Riak. There is now

Re: Yokozuna and Spatial Search

Vincenzo, I replied on the GitHub issue. -Z On Sun, Sep 8, 2013 at 8:23 AM, Vincenzo Vitale wrote: > I got it working with this change to the default conf: > https://github.com/basho/yokozuna/pull/169 > > Before doing this, I first tried creating my own schema but put was > hanging. > > > V. >

Re: riak core dumped, merge_index corruption?

Deyan, What Riak version are you running? There was a corruption issue discovered and fixed in the 1.4.0 release. https://github.com/basho/riak/blob/riak-1.4.0/RELEASE-NOTES.md#issues--prs-resolved https://github.com/basho/merge_index/pull/30 As for fixing, you'll want to delete the buffer file

[ANN] Yokozuna 0.8.0

Riak Users, The eighth release of Yokozuna is out. It is now considered alpha and will soon become part of Riak proper. There could still be breaking changes leading up to the 1.0.0 release which is currently scheduled for early October. The main things of interest this release are the re-targe

Re: Yokozuna kv write timeouts on 1.4 (yz-merge-1.4.0)

to avoid any lingering old dependencies. Let me know if you run into more issues. -Z On Thu, Jul 18, 2013 at 9:33 AM, Ryan Zezeski wrote: > Dave, > > I'm currently in the process re-targeting Yokozuna to 1.4.0 for the 0.8.0 > release. I'll ping this thread when the

Re: Data population of Yokozuna on key-path in schema?

6 PM, Dave Martorana wrote: > Does the JSON extractor work in a similar fashion, or does it follow its > own rules? We don’t use XML anywhere (but JSON everywhere). Thanks! > > Dave > > > On Thu, Jul 18, 2013 at 9:31 AM, Ryan Zezeski wrote: > >> As Eric said, the XML

Re: Riak Search and Sorting

r for Apache Hadoop > > > On Thu, Jul 18, 2013 at 6:55 AM, Ryan Zezeski wrote: > >> Jeremiah, >> >> After a quick glance I don't see anything obvious in the code. I notice >> you have a presort defined. By any chance, if you remove the presort, do >> you

Re: Riak Search and Sorting

Jeremiah, After a quick glance I don't see anything obvious in the code. I notice you have a presort defined. By any chance, if you remove the presort, do you get a correct sorting on the creation_dt field? -Z On Wed, Jul 17, 2013 at 5:30 PM, Jeremiah Peschka < jeremiah.pesc...@gmail.com> wro

Re: Yokozuna kv write timeouts on 1.4 (yz-merge-1.4.0)

; (env)➜ curl -v -H 'content-type: text/plain' -XPUT ' > http://localhost:10018/buckets/players/keys/name' -d "Ryan Zezeski" > * Adding handle: conn: 0x7f995a804000 > * Adding handle: send: 0 > * Adding handle: recv: 0 > * Curl_addHandleToPipeline:

Re: Data population of Yokozuna on key-path in schema?

As Eric said, the XML extractor causes the nested elements to become concatenated by an underscore. "Extractor" is a Yokozuna term. It is the process by which a Riak Object is mapped to a Solr document. In the case of a Riak Object whose value is XML the XML is flattened by a) concatenating nest

Re: [ANN] Yokozuna 0.7.0

h Peschka - Founder, Brent Ozar Unlimited > MCITP: SQL Server 2008, MVP > Cloudera Certified Developer for Apache Hadoop > > > On Mon, Jul 1, 2013 at 8:46 AM, Ryan Zezeski wrote: > >> Riak Users, >> >> Today I'm excited to bring you the 0.7.0 release of Yoko

[ANN] Yokozuna 0.7.0

Riak Users, Today I'm excited to bring you the 0.7.0 release of Yokozuna. It includes some new features such as an upgrade to Solr 4.3.0, isolation of index failures, one-to-many index-to-buckets relationship, and map-reduce support. There is also a performance improvement in index throughput.

Re: Question: Riak search and wildcard

Hi Otto > I will propably make a config file in my app or some temporary > variable which will contain 10 keys which I get with a map/reduce than > is run daily, and then I'll fetch the predefined set from Riak when I > need the "10 first results". Although this will require 10 requests to > get

Re: Anty Entropy Error messages "Cann't allocate memory"

Dmitry, AAE uses leveldb under the hood, which itself has a reliance on mmap. If you attach to one of the Riak nodes (via 'riak attach') what does 'os:cmd("ulimit -v").' say? -Z On Mon, May 6, 2013 at 5:25 PM, Dmitry Aleksandrov wrote: > Anty Entropy Error messages: > > 2013-05-06 17:21:46.00

[ANN] Yokozuna 0.6.0

Riak Users, Today I'm pleased to announce the 0.6.0 release of Yokozuna. Two highlights of this release are: 1. Initial protobuff support at parity with Riak Search. This means that existing Riak clients which have Riak Search/PB support should now be able to query Yokozuna. Please note that,

Re: Deleting from search index but not from bucket

> Is it possible to delete an object from the search index without deleting > it from the bucket? > I'm using Erlang pb client. > > It is possible but not a first-class operation and certainly not supported via the PB client. It would require custom erlang code. -Z ___

Re: Why does Riak Search find one thing and then tell me there were two?

Rob, >>> riak.solr.search('test_riak-search', 'terms:plasma\|en', count=10) > {'max_score': 0.353553, 'num_found': 2, 'docs': []} > > How is this happening? Is 'num_found' supposed to be an accurate count? > Can you try the same query without the count param. I would imagine count maps to 'rows'

Re: "expected_binaries" error in search

Rob, I reproduced this at the command line. Here I'm storing two documents, with > IDs 'doc8' and 'doc9', into a search-enabled bucket named 'test-search'. > > # This command works, even though 'lsh' is empty. I believe this is > because I've never put a field named 'lsh' in this bucket, 'test-sea

Re: Yokozuna max practical bucket limit

Elias, I could see that being something some folks want. From my point of view, I > find that the existing design of one core per bucket may be more useful, so > long as I can search across cores with similar schemas (I created an > issueto track that

Re: Active Anti Entropy with Bitcask Key Expiry

Ben, AAE should not resurrect keys when bitcask expiry is enabled. However, a non-trivial amount of work may be performed if a lot of keys expire all at once. You're correct that the layers above bitcask have no notion of expiry. When a key expires no notification is sent to Riak. This means t

Re: "expected_binaries" error in search

Rob, I don't know what the exact data is. The thing is that it doesn't seem to > cause an error on the client side; it just shows up in the server logs to > be noticed later. > A non-2XX response will be returned. Verify that the response is 200. If it isn't log an error in your app with the ex

Re: "expected_binaries" error in search

Rob, That cryptic error is saying that it expected a binary value type for the field 'ish' ("binary" is a data structure in Erlang) but instead got an empty list. Do you by any chance have the exact data which is causing the issue? If you can isolate the data causing the problems then attach to

Re: Yokozuna max practical bucket limit

Elias, This is exactly why I chose not to make a core per partition. My gut feeling was that most users are likely to have more partitions than indexed buckets. I don't know the overhead per-core or what the limits might be. I would recommend the Solr mailing list for questions like that. I've

Re: Post commit hooks are a single process, so they are executed in the same order as the commits ?

Simon, On Mon, Apr 8, 2013 at 7:14 PM, Simon Majou wrote: > Hello, > > I want to sync a bucket of a first cluster with the bucket of a second > cluster. To do that I think using the post commit hook. > If you didn't know, this is exactly what Riak Enterprise was built to do. I.e. handle multi

Re: AAE and changing the replication factor

Elias, Setting the n_val higher should add the missing replicas. However, setting lower will currently leave the extra replicas alone. This was chosen to err on the side of caution for now. This would be easy enough to verify with a riak_test [1] but I don't think we have one at the moment. -Z

Re: Yokozuna Active Anti-Entropy

Elias, You are correct in that the _yz_ed field (Entropy Data) is the key to AAE. Both KV and YZ build hashtrees for each partition in the ring. Both trees are indexed in real-time as writes come in. Occasionally (default of 1 week) trees are rebuilt from scratch. In the case of Yokozuna a Luc

[ANN] Yokozuna 0.5.0

Riak Users, Today I'm pleased to announce the 0.5.0 release of Yokozuna. This release includes a bit of everything. New features, bug fixes, an upgrade to Solr 4.2.0, and search performance improvement. See the full release notes for more detail. Thank you to @timdoug and @kyleslattery for the

riak-users@lists.basho.com

Tony, Riak Search is treating the '&' the same as 'AND'. If you encode it as %5C%26 it should work. -Z ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: Set the default search schema analyzer_factory to 'standard_analyzer_factory' for all future buckets

On Mon, Mar 4, 2013 at 9:36 AM, vvsanil wrote: > Is there anyway to set the default search schema analyzer_factory to > 'standard_analyzer_factory' for all future buckets (i.e. without having to > manually set schema each time a new bucket is created) ? > Yes, look for the file `default.def` und

Re: How should I avoid words that are effectively stopwords in Riak Search?

Rob, Riak Search doesn't have a traditional term-frequency count. It has something similar but it's an estimate and it is much more expensive than a simple table lookup. Even if it did have term-frequency it doesn't really expose it to the outside world. Not only that, but the standard analyzer

[ANN] Yokozuna 0.4.0

Hello Riak Users, Today I'm pleased to announce the 0.4.0 release of Yokozuna. This is a small release in terms of features added, as there are no new features, but an important release for reasons enumerated below. * Performance improvements to Solr's distributed search thus improving performan

Re: About the node show down when occur riak_searc error of too_many_resut

Jason, Riak Search has a limit of 100k results at which point it halts processing by throwing an exception. It does this to protect itself from having to build an indeterminately sized list and then sort it. You can raise this limit but you might start seeing large process heaps using lots of CP

[ANN] Yokozuna 0.3.0

Riak Users, Today I'm happy to announce the 3rd pre-release of Yokozuna. It's light on new features but has some good performance improvements and added robustness. Here are the highlights: * Allow store/retrieval of schemas via HTTP. * Upgrade to Solr 4.1.0 and the latest Riak. * Improve wri

Re: Riak Search on KV data in erlang terms

Takeshi, The erlang extractors don't work when writing the data via HTTP as they store the data as a binary. I.e. [{"name", "bob"}] becomes <<"[{\"name\", \"bob\"}]">> instead of the proplist you expect. This is because the extractor assumes the object data is already properly decoded. It is po

Yokozuna 0.2.0 [ANN]

Hello Riak Users, For those of you who missed the announcement on Monday, Yokozuna 0.2.0 has been released. This release includes two big features that I discussed in my RICON talk [1] but hadn't yet been completed. 1) Active Anti-Entropy (AAE): This is a process that constantly verifies that th

Re: Riak search query timeout issues with 1.2.1 stable

On Thu, Dec 20, 2012 at 9:51 AM, Abhinav Singh wrote: > > > error.log on riak@172.17.3.82 contains: > 2012-12-20 16:27:37.877 [error] <0.1821.0>@mi_server:handle_info:524 > lookup/range failure: > {{badfun,#Fun},[{mi_server,iterate,6},{mi_server,lookup,8}]} > 2012-12-20 16:27:37.878 [error] emulat

Re: Riak Search - searching across all fields

On Sat, Dec 15, 2012 at 12:43 AM, Matt Painter wrote: > Thanks so much Ryan - yokozuna sounds most promising. If I were building a > small system (relatively simple, small user base) that will be > production-ready in a few months, do you think that Yokozuna could cut the > mustard? I see that it

Re: Riak Search - searching across all fields

Matt, comments inline On Tue, Dec 11, 2012 at 3:35 AM, Matt Painter wrote: > > > Apart from a single default value, is it possible for Riak Search to > search for a keyword across all fields in a document without having to > specify the field up front as a prefix in one's search term? > A field

Re: Riak search query timeout issues with 1.2.1 stable

Hi, comments inline On Wed, Dec 5, 2012 at 8:10 AM, Abhinav Singh wrote: > > > We are facing an issue where search queries works fine on my local dev box > (which have riak-1.2.1rc2 installed). > However same queries timeout on our production boxes (which have > riak-1.2.1 installed): > > 2012-12-

Re: Riak over "LAN" vs "WAN"

On Mon, Nov 19, 2012 at 10:47 AM, Ryan Zezeski wrote: > >> > > The way Riak is designed is far from the most efficient way to replicate > data across a WAN. A lot of that code was/is written with assumptions of > LAN and fairly predictable latency. This is one of

Re: Riak over "LAN" vs "WAN"

Jon, On Mon, Nov 19, 2012 at 3:28 AM, Jon Perez wrote: > > > Why exactly are these reasons? I suspect they have to do with performance. > If so, how exactly does performance degrade when nodes are spread out > between hosts with latencies in the tens to hundred plus milliseconds (as > is > typic

Re: Riak Search Field Aliases

Brian, First, our documentation is wrong. Sorry. The correct way to add aliases looks like so: {field, [ {name, "Name"}, {analyzer_factory, {erlang, text_analyzers, standard_analyzer_factory}}, {alias, "LastName"},

Re: Search not working any more

On Sat, Nov 3, 2012 at 4:33 PM, Martin Streicher wrote: > > > Is there a programmatic way to achieve the equivalent of search-cmd > install zids, so that whenever my application launches, it can enable those > settings? > > Yes. At startup you could add the 'search' bucket property with a value o

Re: Search not working any more

Martin, On Wed, Oct 31, 2012 at 6:01 PM, Martin Streicher < martin.streic...@gmail.com> wrote: > > I deleted my database today using rm -rf on the data directory. I stopped > Riak before the delete, and restarted after recreating that directory with > mkdir. > > Now, I cannot search. > > The dat

Re: Deleting items from search index increases disk usage

Jeremy, On Fri, Nov 2, 2012 at 12:31 PM, Jeremy Raymond wrote: > I cycled through the compaction on another node. Again after 3 rounds > compaction has stopped. On one node the merge index is 26 GB on the other > 21 GB. So it looks like I've hit the 5 segment compaction no-op condition > on both

  1   2   3   4   >