Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 79C5A200C40 for ; Thu, 23 Mar 2017 20:18:42 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 77C1A160B68; Thu, 23 Mar 2017 19:18:42 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 47F94160B83 for ; Thu, 23 Mar 2017 20:18:41 +0100 (CET) Received: (qmail 31733 invoked by uid 500); 23 Mar 2017 19:18:40 -0000 Mailing-List: contact user-help@predictionio.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@predictionio.incubator.apache.org Delivered-To: mailing list user@predictionio.incubator.apache.org Received: (qmail 31681 invoked by uid 99); 23 Mar 2017 19:18:40 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Mar 2017 19:18:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D26A6C132E for ; Thu, 23 Mar 2017 19:18:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.48 X-Spam-Level: ** X-Spam-Status: No, score=2.48 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, JMQ_TRACKER=0.5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=occamsmachete-com.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 9VYa-qIhk45w for ; Thu, 23 Mar 2017 19:18:37 +0000 (UTC) Received: from mail-pg0-f41.google.com (mail-pg0-f41.google.com [74.125.83.41]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 2BA345FAD2 for ; Thu, 23 Mar 2017 19:18:36 +0000 (UTC) Received: by mail-pg0-f41.google.com with SMTP id g2so127766668pge.3 for ; Thu, 23 Mar 2017 12:18:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=occamsmachete-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=SkopFhpN75un3QVafjX8+9+MhVlij9/hR/O7c4XRmT4=; b=PGFmXcQ5UQFx9XznODgEAyTgY9vyurUp2nSPn4G/KKgc28aNmpAYQbUc32K0NNCzjs zRgwVFjM6PwI/wINkEJ8z8Sf3PrsdXCJCqjyt96QqA1pD6bg/ndiKceqwqk6q6tyYGwc b7wBHQozFFg5eXhoGeh96jHTkj/mA3qAL83L/7z1rm6NXZhjU39NGQLlEzw6Krm9rxJU aB8onSSm4rQ2g+lyPZ7tSX+sc4LMAQgTAJOdRLebYXYeRzC5XhHh7aHF3rj6k6Lhkf+F oKrL28xvcgZ3eople6ltvBDQxVbH/eqc2qNYXCs29PE6/F/j4WygY/LJwT2EvQWsdSxb anmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=SkopFhpN75un3QVafjX8+9+MhVlij9/hR/O7c4XRmT4=; b=S3LV8AqnQVOMhkIKBqpPak4HhuKmrcPUucPiphFwlTBu0E7e9txnte6Q4bC7ACdztY HXxyYpF5Ky0a9l2grn6O1zumSUqjW8t3lVUFgGX7tGV8UKPsKpRB/g29dOPbFjdXxMyw iHvPjzqAhinAFRqxTY/J0io8KKiwZNmL69fVZJ1DXi0wysADyllEMtUzehEwciqTJ1GU +BnX0qiccLjht6GZ/8zwvwI3lG3/Pwwgzy92fMHlonpXlT7t3rtcCrbpwLVRSRHxsHIM afLbEHD/ZCFH5l+KajlhtxY1YI0r72Ae273Iv0XSDymPm0TNpyaSP7UWljr4TtWg+wp1 oU/g== X-Gm-Message-State: AFeK/H1QuZn/8MPbZcrEd/OPQX+ANnyRY6MvDhCBIKrg7Z/DhLwcanh1Gys1nFCvrk3DFg== X-Received: by 10.84.215.221 with SMTP id g29mr5835118plj.10.1490296714471; Thu, 23 Mar 2017 12:18:34 -0700 (PDT) Received: from [192.168.0.6] (c-24-18-213-211.hsd1.wa.comcast.net. [24.18.213.211]) by smtp.gmail.com with ESMTPSA id g5sm11904254pgn.18.2017.03.23.12.18.33 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Mar 2017 12:18:33 -0700 (PDT) From: Pat Ferrel Content-Type: multipart/alternative; boundary="Apple-Mail=_1C280388-D7E8-4891-9482-7B8F48BED251" Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Need a Suggessations Date: Thu, 23 Mar 2017 12:18:32 -0700 References: <1467BA7D-F34A-4F7B-9BC7-54B55ECF256A@occamsmachete.com> To: user@predictionio.incubator.apache.org In-Reply-To: Message-Id: <8F051379-4D87-4FB8-BE4A-F6263C59FF31@occamsmachete.com> X-Mailer: Apple Mail (2.3259) archived-at: Thu, 23 Mar 2017 19:18:42 -0000 --Apple-Mail=_1C280388-D7E8-4891-9482-7B8F48BED251 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 The UR uses Elasticsearch for part of the Recommender algorithm, = therefor it must be configured as a storage backend. It is possible to = use Postgres or MySQL for the other stores but we have very little = experience with this. HBase is indefinitely scalable so we always use = that. Single machine deployments are rare with a reasonably sized data = so Elasticsearch + Hbase running separately or in clusters will always = meet the data needs. The RDBs will not and anyway, like I said you have = to use Elasticsearch. Therefore for the UR follow instructions on the ActionML site since they = are specific to the UR. For other templates you may use other = configurations of PIO but if you use the UR config you can also use = every template too. On Mar 23, 2017, at 9:07 AM, Vaghawan Ojha = wrote: Hi, Thank you!=20 I came into further more confusion here, actually I installed prediction = IO version 0.10.0 from here = http://predictionio.incubator.apache.org/install/install-sourcecode/ = = and have been fighting to configure mysql as a storage in my local linux = machine.=20 But I see there is a different documentation of installing in actionml = website, I'm not sure for which I would have to go. Currently there is = no "pio-env.sh". file inside conf folder however there is = pio-env.sh.template file. I commented the pgsql section and uncommented = the mysql section with the username and password, but whenever I do . = sudo PredictionIO-0.10.0-incubating/bin/pio eventserver there seems to = be an error that says that authentication failed with pgsql, however I = don't want to use pgsql.=20 # Storage Repositories # Default is to use PostgreSQL PIO_STORAGE_REPOSITORIES_METADATA_NAME=3Dpio_meta PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=3DPGSQL PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=3Dpio_event PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=3DPGSQL PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=3Dpio_model PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=3DPGSQL # Storage Data Sources # PostgreSQL Default Settings # Please change "pio" to your database name in = PIO_STORAGE_SOURCES_PGSQL_URL # Please change PIO_STORAGE_SOURCES_PGSQL_USERNAME and # PIO_STORAGE_SOURCES_PGSQL_PASSWORD accordingly #PIO_STORAGE_SOURCES_PGSQL_TYPE=3Djdbc #PIO_STORAGE_SOURCES_PGSQL_URL=3Djdbc:postgresql://localhost/pio #PIO_STORAGE_SOURCES_PGSQL_USERNAME=3Dpio #PIO_STORAGE_SOURCES_PGSQL_PASSWORD=3Dpio # MySQL Example PIO_STORAGE_SOURCES_MYSQL_TYPE=3Djdbc PIO_STORAGE_SOURCES_MYSQL_URL=3Djdbc:mysql://localhost/pio PIO_STORAGE_SOURCES_MYSQL_USERNAME=3Droot PIO_STORAGE_SOURCES_MYSQL_PASSWORD=3Droot This is how the pio-env.sh.template looks like. And again when I visited = the actionml site, it suggests that I do have to have ELASTICSEARCH. but = prediction.io site doesn't tells us the same. = Which one should I follow and where would I find the current working = version of installation guide. I actually wanaa use prediction.io = in my production shortly after I implemented in = local.=20 Please help me, thank you very much for your help, I appreciate it so = much. Vaghawan On Thu, Mar 23, 2017 at 9:27 PM, Pat Ferrel > wrote: Since PIO has moved to Apache, the namespace of PIO code changed and so = all templates need to be updated. None of the ones in = https://github.com/PredictionIO/ = will work with Apache PIO. For the upgraded UR see: = https://github.com/actionml/universal-recommender = Docs for the UR are = here: http://actionml.com/docs/ur =20 Also look on the Template gallery page here for a description of = template status. Some have not been moved to the new namespace and = converted to run with PIO but this is pretty easy to do yourself. = http://predictionio.incubator.apache.org/gallery/template-gallery/ = user_id, product_id and purchase_date is all you need to use any = recommender. If you plan to gather other events in the future, use the = UR. As far as item or user based recommendations, the UR will give = either based on the query with the same data and model, as some others = will do. The UR allows you to mix both types in a single query, which = may be useful with small amounts of individual user data. Also the accepted wisdom about this it to put item-based recs on item = detail pages, and user-based recs elsewhere, when you don=E2=80=99t have = an item to base recs on, or in another placement on any page. You can have many different placements of recs in any page by changing = the queries. This is how Netflix gets rows and rows of specialized recs = for different things all based on the same data. The UR queries are = quite flexible. On Mar 23, 2017, at 7:08 AM, Vaghawan Ojha > wrote: Hi,=20 I've been trying to deploy a recommendation system using = https://github.com/PredictionIO/template-scala-parallel-universal-recommen= dation = .=20 I've purchase history of user something like this:=20 user_id, product_id and purchase_date, so I will be using user_id and = product_id to determine the recommendation. I'm not sure if I would be = able to customize the default even parameter.=20 Do you have any suggestions like which template would be more suitable = for my problem. I don't have data like rating or view state, I only have = data about user and product they purchased. I need something like item = based similarity as well as user based item similarity.=20 Any help would be great Thank you Vaghawan --Apple-Mail=_1C280388-D7E8-4891-9482-7B8F48BED251 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 The UR uses Elasticsearch for part of the Recommender = algorithm, therefor it must be configured as a storage backend. It is = possible to use Postgres or MySQL for the other stores but we have very = little experience with this. HBase is indefinitely scalable so we always = use that. Single machine deployments are rare with a reasonably sized = data so Elasticsearch + Hbase running separately or in clusters will = always meet the data needs. The RDBs will not and anyway, like I said = you have to use Elasticsearch.

Therefore for the UR follow instructions on the ActionML site = since they are specific to the UR. For other templates you may use other = configurations of PIO but if you use the UR config you can also use = every template too.


On Mar 23, 2017, at 9:07 AM, Vaghawan = Ojha <vaghawan781@gmail.com> wrote:

Hi, Thank you! 

I came into further more confusion here, actually I installed = prediction IO version 0.10.0 from here http://predictionio.incubator.apache.org/install/install-source= code/  and have been fighting to configure mysql as a storage = in my local linux machine. 

But I see there is a different = documentation of installing in actionml website, I'm not sure for which = I would have to go. Currently there is no "pio-env.sh".  file inside conf folder however = there is pio-env.sh.template file. I commented the pgsql section and = uncommented the mysql section with the username and password, but = whenever I do . sudo PredictionIO-0.10.0-incubating/bin/pio = eventserver there seems to be an error that says that authentication = failed with pgsql, however I don't want to use pgsql. 

# = Storage Repositories

# Default is to use PostgreSQL
PIO_STORAGE_REPOSITORIES_METADATA_NAME=3Dpio_meta
PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=3DPGSQL

PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=3Dpio_event
PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=3DPGSQL

PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=3Dpio_model
PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=3DPGSQL

# Storage Data = Sources

# = PostgreSQL Default Settings
# Please change "pio" = to your database name in PIO_STORAGE_SOURCES_PGSQL_URL
# Please change PIO_STORAGE_SOURCES_PGSQL_USERNAME = and
# PIO_STORAGE_SOURCES_PGSQL_PASSWORD = accordingly
#PIO_STORAGE_SOURCES_PGSQL_TYPE=3Djdbc
#PIO_STORAGE_SOURCES_PGSQL_URL=3Djdbc:postgresql://localhost/pio
#PIO_STORAGE_SOURCES_PGSQL_USERNAME=3Dpio
#PIO_STORAGE_SOURCES_PGSQL_PASSWORD=3Dpio

# MySQL = Example
 PIO_STORAGE_SOURCES_MYSQL_TYPE=3Djdbc
 PIO_STORAGE_SOURCES_MYSQL_URL=3Djdbc:mysql://localhost/pio
 PIO_STORAGE_SOURCES_MYSQL_USERNAME=3Droot
 PIO_STORAGE_SOURCES_MYSQL_PASSWORD=3Droot


This is how the pio-env.sh.template looks like. And again = when I visited the actionml site, it suggests that I do have to have = ELASTICSEARCH. but prediction.io site doesn't tells us the same. Which one = should I follow and where would I find the current working version of = installation guide. I actually wanaa use prediction.io in my production shortly after I = implemented in local. 

Please help me, thank you very much for your help, I = appreciate it so much.
Vaghawan


On Thu, Mar 23, 2017 at 9:27 PM, Pat Ferrel <pat@occamsmachete.com> = wrote:
Since PIO has moved to Apache, = the namespace of PIO code changed and so all templates need to be = updated. None of the ones in  https://github.com/PredictionIO/ will work with Apache PIO. For the = upgraded UR see: https://github.com/actionml/universal-recommender Docs for the UR are = here: http://actionml.com/docs/ur 

Also look on the = Template gallery page here for a description of template status. Some = have not been moved to the new namespace and converted to run with PIO = but this is pretty easy to do yourself. http://predictionio.incubator.apache.org/gallery/template-gallery/

user_id, product_id and purchase_date = is all you need to use any recommender. If you plan to gather other = events in the future, use the UR. As far as item or user based = recommendations, the UR will give either based on the query with the = same data and model, as some others will do. The UR allows you to mix = both types in a single query, which may be useful with small amounts of = individual user data.

Also the accepted wisdom about this it to put item-based recs = on item detail pages, and user-based recs elsewhere, when you don=E2=80=99= t have an item to base recs on, or in another placement on any = page.

You can = have many different placements of recs in any page by changing the = queries. This is how Netflix gets rows and rows of specialized recs for = different things all based on the same data. The UR queries are quite = flexible.


On Mar 23, 2017, at 7:08 AM, Vaghawan Ojha <vaghawan781@gmail.com> wrote:

Hi, 

I've been trying to deploy a = recommendation system using https://github.com/PredictionIO/template-scala-parallel-universal-recommendation. 

I've purchase history of user something = like this: 
user_id, product_id and = purchase_date, so I will be using user_id and product_id to determine = the recommendation. I'm not sure if I would be able to customize the = default even parameter. 

Do you have any suggestions like which = template would be more suitable for my problem. I don't have data like = rating or view state, I only have data about user and product they = purchased. I need something like item based similarity as well as user = based item similarity. 

Any help would be great

Thank you
Vaghawan



= --Apple-Mail=_1C280388-D7E8-4891-9482-7B8F48BED251--