From commits-return-5527-archive-asf-public=cust-asf.ponee.io@predictionio.apache.org Sat Nov 3 21:48:51 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 086C718066B for ; Sat, 3 Nov 2018 21:48:47 +0100 (CET) Received: (qmail 66677 invoked by uid 500); 3 Nov 2018 20:48:47 -0000 Mailing-List: contact commits-help@predictionio.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@predictionio.apache.org Delivered-To: mailing list commits@predictionio.apache.org Received: (qmail 66668 invoked by uid 99); 3 Nov 2018 20:48:47 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Nov 2018 20:48:47 +0000 Received: by gitbox.apache.org (ASF Mail Server at gitbox.apache.org, from userid 33) id 18E3D81E0E; Sat, 3 Nov 2018 20:48:46 +0000 (UTC) Date: Sat, 03 Nov 2018 20:48:46 +0000 To: "commits@predictionio.apache.org" Subject: [predictionio-site] branch asf-site updated: Documentation based on apache/predictionio#a956efc2a652ad0842cb14a14f9d76b164bd0dd6 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Message-ID: <154127812601.10017.2760579663723162222@gitbox.apache.org> From: git-site-role@apache.org X-Git-Host: gitbox.apache.org X-Git-Repo: predictionio-site X-Git-Refname: refs/heads/asf-site X-Git-Reftype: branch X-Git-Oldrev: e0e1c9a0973993212c042fd9e749426379550672 X-Git-Newrev: db417de9e0591570684a33e9d26e535fb74a775f X-Git-Rev: db417de9e0591570684a33e9d26e535fb74a775f X-Git-NotificationType: ref_changed_plus_diff X-Git-Multimail-Version: 1.5.dev Auto-Submitted: auto-generated This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/predictionio-site.git The following commit(s) were added to refs/heads/asf-site by this push: new db417de Documentation based on apache/predictionio#a956efc2a652ad0842cb14a14f9d76b164bd0dd6 db417de is described below commit db417de9e0591570684a33e9d26e535fb74a775f Author: jenkins AuthorDate: Sat Nov 3 20:48:44 2018 +0000 Documentation based on apache/predictionio#a956efc2a652ad0842cb14a14f9d76b164bd0dd6 --- archived/launch-aws/index.html | 6 + datacollection/batchimport/index.html | 4 +- datacollection/channel/index.html | 6 +- datacollection/eventapi/index.html | 20 +- gallery/template-gallery/index.html | 2 +- install/index.html | 2 +- install/install-docker/index.html | 54 ++++ install/launch-aws/index.html | 6 - samples/tabs/index.html | 18 +- sitemap.xml | 272 +++++++++++---------- templates/classification/quickstart/index.html | 30 +-- .../complementarypurchase/quickstart/index.html | 20 +- .../ecommercerecommendation/quickstart/index.html | 60 ++--- .../quickstart/index.html | 60 ++--- templates/leadscoring/quickstart/index.html | 30 +-- templates/productranking/quickstart/index.html | 40 +-- templates/recommendation/quickstart/index.html | 30 +-- templates/similarproduct/quickstart/index.html | 40 +-- templates/vanilla/quickstart/index.html | 10 +- 19 files changed, 385 insertions(+), 325 deletions(-) diff --git a/archived/launch-aws/index.html b/archived/launch-aws/index.html new file mode 100644 index 0000000..820b1f8 --- /dev/null +++ b/archived/launch-aws/index.html @@ -0,0 +1,6 @@ +Launching PredictionIO on AWS \ No newline at end of file diff --git a/datacollection/batchimport/index.html b/datacollection/batchimport/index.html index 1c93c3c..93740a1 100644 --- a/datacollection/batchimport/index.html +++ b/datacollection/batchimport/index.html @@ -7,7 +7,7 @@ {"event":"rate","entityType":"user","entityId":"3","targetEntityType":"item",{"event":"buy","entityType":"user","entityId":"3","targetEntityType":"item",{"event":"buy","entityType":"user","entityId":"3","targetEntityType":"item",

Please make sure your import file does not contain any empty lines. Empty lines will be treated as a null object and will return an error during import.

Use SDK to Prepare Batch Input File

Some of the Apache PredictionIO SDKs also provides FileExporter client. You may use them to prepare the JSON file as described above. [...] +

Please make sure your import file does not contain any empty lines. Empty lines will be treated as a null object and will return an error during import.

Use SDK to Prepare Batch Input File

Some of the Apache PredictionIO SDKs also provides FileExporter client. You may use them to prepare the JSON file as described above. [...] 2 3 4 @@ -58,7 +58,7 @@ # close the FileExporter when finish writing all events exporter.close() -

(coming soon) 
1
 
(coming  (coming soon)  
 
 
 
1
 
(coming 
  
After a brief while, the tool should return to the console without any error. Congratulations! You have successfully imported your events.
 
 
 
 
 (TODO: update me) 
 
 
 
 
1
+
 
 
 
 
 (TODO: update me) 
 
 
 
 
1
 2
 3
 4
@@ -80,7 +80,7 @@
     properties=event_properties,
     event_time=datetime(2014, 12, 13, 21, 38, 45, 618000,  (TODO: update me)  
 
 
 
1
 
(coming 
 
 
 
 
 (TODO: update me) 
 
 
 
 
1
 
(coming 
 
 
 
  
You can also follow the EventAPI debug receipts to query the events of specific channel by adding the channel query parameter in the URL.
Delete a Channel (including all imported data)
1
pio app data-delete <app name> --channel <channel name>
 
  
Accessing Channel Data in Engine
To acccess channel data, simply specify the channel name when use the PEventStore or LEventStore API. Data is read from from the default channel if channelName is not specified.
For example, read data from default channel:
[INFO] [App$]         Name: MyTestApp
 [INFO] [App$]           ID: 6
 [INFO] [App$]   Access Key: WPgcXKd42FPQpZHVbVeMyqF4CQJUnXQmIMTHhX3ZUrSzvy1KXJjdFUrslifa9rnB
-
 
 
Creating Your First Event
You may connect to the Event Server with HTTP request or by using one of many Apache PredictionIO SDKs.
For example, the following shows how one can create an event involving a single entity. Replace the value of accessKey by the Access Key generated for your App.
 
     
 
 
Creating Your First Event
You may connect to the Event Server with HTTP request or by using one of many Apache PredictionIO SDKs.
For example, the following shows how one can create an event involving a single entity. Replace the value of accessKey by the Access Key generated for your App.
 
     
  • 
-
 
 
 
 
 
 
 
1
+
 
 
 
 
 
 
 
1
 2
 3
 4
@@ -94,7 +94,7 @@ Content-Length: 18
                         'eventTime' => '2004-12-13T21:39:45.618-07:00'
                        ));
 ?>
-
 
 
 
 
 
 
 
1
+
 
 
 
 
 
 
 
1
 2
 3
 4
@@ -137,7 +137,7 @@ Content-Length: 18
     properties=first_event_properties,
     event_time=first_event_time,
 )
-
 
 
 
 
 
 
 
1
+
 
 
 
 
 
 
 
1
 2
 3
 4
@@ -158,8 +158,8 @@ Content-Length: 18
                                             'prop4' => true,
                                             'prop5' => %w(a b c),
                                             'prop6' => 4.56 })
-
 
 
 
 
 
 
 
1
 
(coming soon)
-
 
 
 
  
For example, the following shows how one can create an event involving two entities (with targetEntity).
 
1
 
(coming soon)
+

For example, the following shows how one can create an event involving two entities (with targetEntity).

1
+
 
1
 2
 3
 4
@@ -221,7 +221,7 @@ Content-Length: 18
                         'eventTime' => '2004-12-13T21:39:45.618Z'
                        ));
 ?>
-
 
1
+
 
1
 2
 3
 4
@@ -246,7 +246,7 @@ Content-Length: 18
     target_entity_id="iid",
     properties=second_event_properties,
     event_time=datetime(2014, 12, 13, 21, 38, 45, 618000,  
 
 
1
+
 
 
  
 
 
 
1
 2
 3
 4
@@ -263,7 +263,7 @@ Content-Length: 18
                           'eventTime' => '2004-12-13T21:39:45.618Z',
                           'properties' => { 'someProperty' => 'value1',
                                             'anotherProperty' => 'value2' })
-
 
 
 
 
 
 
 
1
 
(coming soon)
+
 
 
 
 
 
 
 
1
 
(coming soon)
 
 
 
 
  
Sample response:
1
 2
 3
diff --git a/gallery/template-gallery/index.html b/gallery/template-gallery/index.html
index 5bf0367..44cc67c 100644
--- a/gallery/template-gallery/index.html
+++ b/gallery/template-gallery/index.html
@@ -1,4 +1,4 @@
-Engine Template Gallery
git clone https://github.com/apache/predictionio.git
+cd predictionio/docker
+
 
 
In this installation, we only need the docker sub-directory in the repository. One can use other tools to get the folder without cloning the whole project.
Build Docker Image
To build PredictionIO docker image, Dockerfile is provided in sub-directory pio.
People can get PredictionIO image from Dockerhub through docker pull predictionio/pio. However, since the image cannot run without a properly configured storage, please follow the following steps to complete the installation.
Image predic [...]
+2
+3
+4
+5
+6
docker-compose -f docker-compose.yml \
+    -f pgsql/docker-compose.base.yml \
+    -f pgsql/docker-compose.meta.yml \
+    -f pgsql/docker-compose.event.yml \
+    -f pgsql/docker-compose.model.yml \
+    up
+
 
 
In this examples, we pull and start predictionio/pio image with docker-compose.yml.
And pull postgres:9 image with pgsql/docker-compose.base.yml.
And config PostgreSQL to store our metadata, event, and model with pgsql/docker-compose.meta.yml, pgsql/docker-compose.event.yml, and pgsql/docker-compose.model.yml.
After pulling the images, th [...]
+2
+3
+4
+5
...
+pio_1       | [INFO] [Management$] Your system is all ready to go.
+pio_1       | [INFO] [Management$] Creating Event Server at 0.0.0.0:7070
+pio_1       | [INFO] [HttpListener] Bound to /0.0.0.0:7070
+pio_1       | [INFO] [EventServerActor] Bound received. EventServer is ready.
+

Verifying Service

A command tool pio-docker is provided to invoke pio command in the PredictionIO container. Set pio-docker to default execution path and use status to check the current PredictionIO service with the following script.

$ export PATH=`pwd`/bin:$PATH
+$ pio-docker status
+

One should be able to see the corresponding log in the following structure, and your system is ready to go!

1
+2
+3
+4
+5
+6
+7
+8
+9
+10
+11
[INFO] [Management$] Inspecting PredictionIO...
+[INFO] [Management$] PredictionIO 0.13.0 is installed at /usr/share/predictionio
+[INFO] [Management$] Inspecting Apache Spark...
+[INFO] [Management$] Apache Spark is installed at /usr/share/spark-2.2.2-bin-hadoop2.7
+[INFO] [Management$] Apache Spark 2.2.2 detected (meets minimum requirement of 1.3.0)
+[INFO] [Management$] Inspecting storage backend connections...
+[INFO] [Storage$] Verifying Meta Data Backend (Source: PGSQL)...
+[INFO] [Storage$] Verifying Model Data Backend (Source: PGSQL)...
+[INFO] [Storage$] Verifying Event Data Backend (Source: PGSQL)...
+[INFO] [Storage$] Test writing to Event Store (App Id 0)...
+[INFO] [Management$] Your system is all ready to go.
+

After the service is up, one can continue by changing pio to pio-docker for further deployment. More details are provided in this document.

Community Docker Support

More PredictionIO Docker p [...] +(w[n].q=w[n].q||[]).push(arguments);};s=d.createElement(t); +e=d.getElementsByTagName(t)[0];s.async=1;s.src=u;e.parentNode.insertBefore(s,e); +})(window,document,'script','//s.swiftypecdn.com/install/v1/st.js','_st'); + +_st('install','HaUfpXXV87xoB_zzCQ45'); \ No newline at end of file diff --git a/install/launch-aws/index.html b/install/launch-aws/index.html deleted file mode 100644 index bfcde65..0000000 --- a/install/launch-aws/index.html +++ /dev/null @@ -1,6 +0,0 @@ -Launching PredictionIO on AWS \ No newline at end of file diff --git a/samples/tabs/index.html b/samples/tabs/index.html index 55fba89..ada2487 100644 --- a/samples/tabs/index.html +++ b/samples/tabs/index.html @@ -1,4 +1,4 @@ -Tabs [...] +Tabs [...] 2 3 4 @@ -9,11 +9,11 @@ 'bar' end end -

This is a test of **markdown** inside a tab! 
1
+
This is a test of **markdown** inside a tab! 
1
 2
 
// This tab does not have the data-lang attribute set!
 $ cd path/to/your/file
-
 
1
 
<p>Yes you can still use HTML in code blocks!</p>
-
 
1
+
 
1
 
<p>Yes you can still use HTML in code blocks!</p>
+
 
1
 2
 3
 4
@@ -28,7 +28,7 @@ Test 5 =>
 Test 6 <=
 Test 7 <>
 <p><b>Test</b></p>
-

Test Syncing

Here we show a similar set of tabs to test language syncing:

Test Syncing

Here we show a similar set of tabs to test language syncing:

This is a test of **markdown** inside a tab! 
1
+
This is a test of **markdown** inside a tab! 
1
 2
 
// This tab does not have the data-lang attribute set!
 $ cd path/to/your/file
-

This HTML is hard coded.

1
 
# The other group does not ha [...]
-
 
 
 
 
 
 This includes **bold** with Markdown.