| commit | aaa45ef2e495c5fb32e9105d701797c33125a7e3 | [log] [tgz] |
|---|---|---|
| author | David Singer <david@ramaboo.com> | Mon Mar 30 13:14:05 2015 -0700 |
| committer | David Singer <david@ramaboo.com> | Mon Mar 30 13:14:05 2015 -0700 |
| tree | a95e8c4c8dcfef0da180dd89205d624965fa7854 | |
| parent | dbb114c119e801b9636642df070d34f19ee20396 [diff] |
Adding json dependancy
The Ruby SDK provides a convenient wrapper for the PredictionIO API. It allows you to quickly record your users' behavior and retrieve personalized predictions for them.
Ruby 1.9.3+ required!
The module is published to RubyGems and can be installed directly by:
gem install predictionio
Or using Bundler with:
gem 'predictionio', '0.9.0'
Connect to the Event Server with:
# Define environment variables. ENV['PIO_THREADS'] = 50 # For async requests. ENV['PIO_EVENT_SERVER_URL'] = 'http://localhost:7070' ENV['PIO_ACCESS_KEY'] = 'YOUR_ACCESS_KEY' # Find your access key with: `$ pio app list`. # Create PredictionIO event client. client = PredictionIO::EventClient.new(ENV['PIO_ACCESS_KEY'], ENV['PIO_EVENT_SERVER_URL'], ENV['PIO_THREADS'])
user_id = User.find(...).id client.create_event( '$set', 'user', user_id )
item_id = Model.find(...).id client.create_event( '$set', 'item', item_id, { 'properties' => { 'categories' => ['Category 1', 'Category 2'] } } )
client.create_event( 'rate', 'user', user_id, { 'targetEntityType' => 'item', 'targetEntityId' => item_id, 'properties' => { 'rating' => 10 } } )
To use an async request simply change create_event to acreate_event. The asynchronous method wont though an error though so it's best to start with the synchronous one.
Connect to the PredictionIO Engine with:
# Define environmental variables. ENV['PIO_ENGINE_URL'] = 'http://localhost:8000' # Create PredictionIO engine client. client = PredictionIO::EngineClient.new(ENV['PIO_ENGINE_URL'])
# Get 5 recommendations for items similar to 10, 20, 30. response = client.send_query(items: [10, 20, 30], num: 5)
RDoc is available online.
View Google Group
Use JIRA or GitHub Issues.
We follow the [git-flow] (http://nvie.com/posts/a-successful-git-branching-model/) model where all active development goes to the develop branch, and releases go to the master branch. Pull requests should be made against the develop branch and include relevant tests, if applicable. Please sign our Contributor Agreement before submitting a pull request.