See below an example *.* It seems you copied the content twice in fact
*#!/usr/bin/env bash## Copy this file as pio-env.sh and edit it for your site's configuration.## Licensed to the Apache Software Foundation (ASF) under one or more# contributor license agreements. See the NOTICE file distributed with# this work for additional information regarding copyright ownership.# The ASF licenses this file to You under the Apache License, Version 2.0# (the "License"); you may not use this file except in compliance with# the License. You may obtain a copy of the License at## http://www.apache.org/licenses/LICENSE-2.0 <http://www.apache.org/licenses/LICENSE-2.0>## Unless required by applicable law or agreed to in writing, software# distributed under the License is distributed on an "AS IS" BASIS,# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.# See the License for the specific language governing permissions and# limitations under the License.## PredictionIO Main Configuration## This section controls core behavior of PredictionIO. It is very likely that# you need to change these to fit your site.# SPARK_HOME: Apache Spark is a hard dependency and must be configured.SPARK_HOME=$PIO_HOME/vendors/spark-1.5.1-bin-hadoop2.6POSTGRES_JDBC_DRIVER=$PIO_HOME/lib/postgresql-9.4-1204.jdbc41.jarMYSQL_JDBC_DRIVER=$PIO_HOME/lib/mysql-connector-java-5.1.37.jar# ES_CONF_DIR: You must configure this if you have advanced configuration for# your Elasticsearch setup.# ES_CONF_DIR=/opt/elasticsearch# HADOOP_CONF_DIR: You must configure this if you intend to run PredictionIO# with Hadoop 2.# HADOOP_CONF_DIR=/opt/hadoop# HBASE_CONF_DIR: You must configure this if you intend to run PredictionIO# with HBase on a remote cluster.# HBASE_CONF_DIR=$PIO_HOME/vendors/hbase-1.0.0/conf# Filesystem paths where PredictionIO uses as block storage.PIO_FS_BASEDIR=$HOME/.pio_storePIO_FS_ENGINESDIR=$PIO_FS_BASEDIR/enginesPIO_FS_TMPDIR=$PIO_FS_BASEDIR/tmp# PredictionIO Storage Configuration## This section controls programs that make use of PredictionIO's built-in# storage facilities. Default values are shown below.## For more information on storage configuration please refer to# http://predictionio.incubator.apache.org/system/anotherdatastore/ <http://predictionio.incubator.apache.org/system/anotherdatastore/># Storage Repositories# Default is to use PostgreSQLPIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_metaPIO_STORAGE_REPOSITORIES_METADATA_SOURCE=MYSQLPIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_eventPIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=MYSQLPIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_modelPIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=MYSQL# 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=jdbc#PIO_STORAGE_SOURCES_PGSQL_URL=jdbc:postgresql://localhost/pio#PIO_STORAGE_SOURCES_PGSQL_USERNAME=pio#PIO_STORAGE_SOURCES_PGSQL_PASSWORD=pio# MySQL Example PIO_STORAGE_SOURCES_MYSQL_TYPE=jdbc PIO_STORAGE_SOURCES_MYSQL_URL=jdbc:mysql://localhost/pio PIO_STORAGE_SOURCES_MYSQL_USERNAME=pio PIO_STORAGE_SOURCES_MYSQL_PASSWORD=pio# Elasticsearch Example# PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch# PIO_STORAGE_SOURCES_ELASTICSEARCH_CLUSTERNAME=<elasticsearch_cluster_name># PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS=localhost# PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300# PIO_STORAGE_SOURCES_ELASTICSEARCH_HOME=$PIO_HOME/vendors/elasticsearch-1.4.4# Local File System ExamplePIO_STORAGE_SOURCES_LOCALFS_TYPE=localfsPIO_STORAGE_SOURCES_LOCALFS_PATH=$PIO_FS_BASEDIR/models# HBase Example# PIO_STORAGE_SOURCES_HBASE_TYPE=hbase# PIO_STORAGE_SOURCES_HBASE_HOME=$PIO_HOME/vendors/hbase-1.0.0* 2017-03-23 22:06 GMT+04:00 Ambuj Sharma <[email protected]>: > check your pio-env.sh. Every configuration is copied twice > > > Thanks and Regards > Ambuj Sharma > Sunrise may late, But Morning is sure..... > Team ML > Betaout > > On Thu, Mar 23, 2017 at 11:26 PM, Vaghawan Ojha <[email protected]> > wrote: > >> Still got the same unfortunately: >> >> this is pio status >> >> ionIO-0.10.0-incubating/bin/pio status >> [INFO] [Console$] Inspecting PredictionIO... >> [INFO] [Console$] PredictionIO 0.10.0-incubating is installed at >> /var/www/apache-predictionio-0.10.0-incubating/PredictionIO- >> 0.10.0-incubating >> [INFO] [Console$] Inspecting Apache Spark... >> [INFO] [Console$] Apache Spark is installed at >> /var/www/apache-predictionio-0.10.0-incubating/PredictionIO- >> 0.10.0-incubating/vendors/spark-1.5.1-bin-hadoop2.6 >> [INFO] [Console$] Apache Spark 1.5.1 detected (meets minimum requirement >> of 1.3.0) >> [INFO] [Console$] Inspecting storage backend connections... >> [INFO] [Storage$] Verifying Meta Data Backend (Source: PGSQL)... >> [ERROR] [Console$] Unable to connect to all storage backends >> successfully. The following shows the error message from the storage >> backend. >> [ERROR] [Console$] FATAL: password authentication failed for user "pio" >> (org.postgresql.util.PSQLException) >> [ERROR] [Console$] Dumping configuration of initialized storage backend >> sources. Please make sure they are correct. >> [ERROR] [Console$] Source Name: PGSQL; Type: jdbc; Configuration: URL -> >> jdbc:postgresql://localhost/pio, PASSWORD -> pio, TYPE -> jdbc, USERNAME >> -> pio >> >> and I've attacted the pio-env.sh. Any help? >> >> On Thu, Mar 23, 2017 at 11:37 PM, Ambuj Sharma <[email protected]> >> wrote: >> >>> copy pio-env.sh.template to pio-env.sh. >>> >>> >>> Thanks and Regards >>> Ambuj Sharma >>> Sunrise may late, But Morning is sure..... >>> Team ML >>> Betaout >>> >>> On Thu, Mar 23, 2017 at 11:13 PM, Vaghawan Ojha <[email protected]> >>> wrote: >>> >>>> There is no file called pio-env.sh however there is >>>> pio-env.sh.template. Are they the same? >>>> >>>> On Thu, Mar 23, 2017 at 11:11 PM, Marius Rabenarivo < >>>> [email protected]> wrote: >>>> >>>>> # Default is to use PostgreSQL >>>>> PIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_meta >>>>> PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=MYSQL >>>>> >>>>> PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event >>>>> PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=MYSQL >>>>> >>>>> PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model >>>>> PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=MYSQL >>>>> >>>>> >>>>> 2017-03-23 21:24 GMT+04:00 Marius Rabenarivo < >>>>> [email protected]>: >>>>> >>>>>> You have to change the config in pio-env.sh to use MYSQL instead of >>>>>> PGSQL >>>>>> >>>>>> In the pasted response above I can read Verifying Meta Data Backend >>>>>> (Source: PGSQL)... >>>>>> >>>>>> 2017-03-23 21:19 GMT+04:00 Vaghawan Ojha <[email protected]>: >>>>>> >>>>>>> Yes following is the response of pio status >>>>>>> >>>>>>> sudo PredictionIO-0.10.0-incubating/bin/pio status >>>>>>> [INFO] [Console$] Inspecting PredictionIO... >>>>>>> [INFO] [Console$] PredictionIO 0.10.0-incubating is installed at >>>>>>> /home/ekbana-php/Downloads/apache-predictionio-0.10.0-incuba >>>>>>> ting/PredictionIO-0.10.0-incubating >>>>>>> [INFO] [Console$] Inspecting Apache Spark... >>>>>>> [INFO] [Console$] Apache Spark is installed at >>>>>>> /home/ekbana-php/Downloads/apache-predictionio-0.10.0-incuba >>>>>>> ting/PredictionIO-0.10.0-incubating/vendors/spark-1.5.1-bin- >>>>>>> hadoop2.6 >>>>>>> [INFO] [Console$] Apache Spark 1.5.1 detected (meets minimum >>>>>>> requirement of 1.3.0) >>>>>>> [INFO] [Console$] Inspecting storage backend connections... >>>>>>> [INFO] [Storage$] Verifying Meta Data Backend (Source: PGSQL)... >>>>>>> [ERROR] [Console$] Unable to connect to all storage backends >>>>>>> successfully. The following shows the error message from the storage >>>>>>> backend. >>>>>>> [ERROR] [Console$] FATAL: password authentication failed for user >>>>>>> "pio" (org.postgresql.util.PSQLException) >>>>>>> [ERROR] [Console$] Dumping configuration of initialized storage >>>>>>> backend sources. Please make sure they are correct. >>>>>>> [ERROR] [Console$] Source Name: PGSQL; Type: jdbc; Configuration: >>>>>>> URL -> jdbc:postgresql://localhost/pio, PASSWORD -> pio, TYPE -> >>>>>>> jdbc, USERNAME -> pio >>>>>>> >>>>>>> Which says that postgresql authentication failed. Ok I'm trying to >>>>>>> go for postgresql this time instead of mysql, I don't wanna lose much >>>>>>> time >>>>>>> fighting with this two sql. I can use any of them, it just need to work. >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> On Thu, Mar 23, 2017 at 11:00 PM, Marius Rabenarivo < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> How do you start the services? >>>>>>>> >>>>>>>> The is a script named pio-start-all in $PIO_HOME/bin to do it you >>>>>>>> can check it to see what you have to start before using pio commands. >>>>>>>> >>>>>>>> Try doing pio status to check if all required services are running >>>>>>>> properly. >>>>>>>> >>>>>>>> 2017-03-23 21:04 GMT+04:00 Vaghawan Ojha <[email protected]>: >>>>>>>> >>>>>>>>> Yes that's what I wanted to do, but couldn't come out to configure >>>>>>>>> it. No matter how much I change in the pio-env.sh.template, when I >>>>>>>>> start >>>>>>>>> the event server it always pops up with the posgresql error of >>>>>>>>> authentication. >>>>>>>>> >>>>>>>>> I even tried with posgresql and it shows the same things. Party >>>>>>>>> something to do with my dumbness I guess. >>>>>>>>> >>>>>>>>> Thank you very much Marius. >>>>>>>>> >>>>>>>>> On Thu, Mar 23, 2017 at 10:39 PM, Marius Rabenarivo < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> You can use MySQL as event store but you need ElasticSearch to >>>>>>>>>> store the model metadata and index used by UR Engine. >>>>>>>>>> >>>>>>>>>> 2017-03-23 20:25 GMT+04:00 Vaghawan Ojha <[email protected]>: >>>>>>>>>> >>>>>>>>>>> But I wanted to use mysql as default. Should I switch it? I can >>>>>>>>>>> do that, but I was just wondering since the documentation says that >>>>>>>>>>> I could >>>>>>>>>>> use mysql. >>>>>>>>>>> >>>>>>>>>>> On Thu, Mar 23, 2017 at 10:03 PM, Marius Rabenarivo < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> I think pio-start-all start PostgreSQL by default >>>>>>>>>>>> >>>>>>>>>>>> 2017-03-23 20:16 GMT+04:00 Vaghawan Ojha <[email protected] >>>>>>>>>>>> >: >>>>>>>>>>>> >>>>>>>>>>>>> Hi, >>>>>>>>>>>>> >>>>>>>>>>>>> Yes I did that but still I get the same output, it's weird. >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Mar 23, 2017 at 10:00 PM, Marius Rabenarivo < >>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> You have to change this section >>>>>>>>>>>>>> >>>>>>>>>>>>>> # Default is to use PostgreSQL >>>>>>>>>>>>>> PIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_meta >>>>>>>>>>>>>> PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=PGSQL >>>>>>>>>>>>>> >>>>>>>>>>>>>> PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event >>>>>>>>>>>>>> PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=PGSQL >>>>>>>>>>>>>> >>>>>>>>>>>>>> PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model >>>>>>>>>>>>>> PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=PGSQL >>>>>>>>>>>>>> >>>>>>>>>>>>>> Put MYSQL in place of PGSQL >>>>>>>>>>>>>> >>>>>>>>>>>>>> 2017-03-23 20:07 GMT+04:00 Vaghawan Ojha < >>>>>>>>>>>>>> [email protected]>: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> 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/instal >>>>>>>>>>>>>>> l-sourcecode/ 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=pio_meta >>>>>>>>>>>>>>> PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=PGSQL >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event >>>>>>>>>>>>>>> PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=PGSQL >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model >>>>>>>>>>>>>>> PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=PGSQL >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> # 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=jdbc >>>>>>>>>>>>>>> #PIO_STORAGE_SOURCES_PGSQL_URL=jdbc:postgresql://localhost/p >>>>>>>>>>>>>>> io >>>>>>>>>>>>>>> #PIO_STORAGE_SOURCES_PGSQL_USERNAME=pio >>>>>>>>>>>>>>> #PIO_STORAGE_SOURCES_PGSQL_PASSWORD=pio >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> # MySQL Example >>>>>>>>>>>>>>> PIO_STORAGE_SOURCES_MYSQL_TYPE=jdbc >>>>>>>>>>>>>>> PIO_STORAGE_SOURCES_MYSQL_URL=jdbc:mysql://localhost/pio >>>>>>>>>>>>>>> PIO_STORAGE_SOURCES_MYSQL_USERNAME=root >>>>>>>>>>>>>>> PIO_STORAGE_SOURCES_MYSQL_PASSWORD=root >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 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 < >>>>>>>>>>>>>>> [email protected]> 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/ >>>>>>>>>>>>>>>> <https://github.com/PredictionIO/template-scala-parallel-universal-recommendation> >>>>>>>>>>>>>>>> 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’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 < >>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I've been trying to deploy a recommendation system using >>>>>>>>>>>>>>>> https://github.com/PredictionIO/template-scala-paralle >>>>>>>>>>>>>>>> l-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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >
