What about Ubuntu? (assuming your usual Debian package works for Ubuntu)

On Mon, Jun 13, 2011 at 3:37 PM, Sean Cribbs <[email protected]> wrote:

> Sorry, I've been corrected by our release manager. We have quit building
> and supporting 32-bit binaries for RHEL as of 0.14.x (0.14.0 was the last,
> and a manual build at that).  Unless strong demand appears for a 32-bit RHEL
> package, we won't be releasing any more.
>
>
> Sean Cribbs <[email protected]>
> Developer Advocate
> Basho Technologies, Inc.
> http://basho.com/
>
> On Jun 13, 2011, at 5:15 PM, Thomas Fee wrote:
>
> I noticed the riak-search prebuilt binaries for RedHat are all 64bits. Is
> this merely a reflection of memory needs or of something more fundamental?
> Mainly for development and QA, it would be bad if the unified riak couldn't
> be downloaded and installed for 32bits.
>
>
> On Mon, Jun 13, 2011 at 3:09 PM, Ryan Zezeski <[email protected]> wrote:
>
>> Riak Users,
>>
>> I'm happy to announce that Riak Search has now been integrated with Riak
>> in the master branch.
>>
>>
>> https://github.com/basho/riak/commit/1a4daa717ce9bb627e72fb7c32dda2ec84e02e92
>>
>> To use Search you no longer checkout the riak_search repo.  Instead, you
>> checkout riak, build a release as you usually would, and then enable the
>> Search functionality.  It should be fairly obvious how to do this by looking
>> at `app.config` but there is a small README in the riak_search repo going
>> over this (which I should probably move into the Riak README).
>>
>> https://github.com/basho/riak_search
>>
>> Along with the integration work we have also decided to drop support for
>> JVM based analyzers (i.e. the Qilr application was removed).  While our
>> analyzers are not nearly as sophisticated as what is provided by Lucene we
>> engaged with the community and our customers and found that very few, if
>> any, are making use of this functionality.  Considering the cruft and
>> general awkwardness this caused to the riak_search code base we figured it
>> was best to remove this support for now.  Furthermore, this support was not
>> free in that there was overhead that had to be paid for talking with the
>> JVM instances running these analyzers.  This doesn't mean we won't possibly
>> support more advanced analyzers in the future but for now we have what we
>> need for the majority of use cases.
>>
>> Finally, please bear with us while we update documentation and refine the
>> Search/Riak integration over the next couple of months.
>>
>> -Ryan
>>
>> _______________________________________________
>> riak-users mailing list
>> [email protected]
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>
>>
> _______________________________________________
> riak-users mailing list
> [email protected]
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
>
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to