Why are these going to the incubator address?

2018-08-24 Thread Pat Ferrel
Is it necessary these commits are going to the incubator list? Are
notifications setup wrong?


From: git-site-r...@apache.org 

Reply: dev@predictionio.apache.org 

Date: August 24, 2018 at 10:33:34 AM
To: comm...@predictionio.incubator.apache.org


Subject:  [7/7] predictionio-site git commit: Documentation based on <

comm...@predictionio.incubator.apache.org>

apache/predictionio#fc481c9c82989e1b484ea5bfeb540bc96758bed5

Documentation based on
apache/predictionio#fc481c9c82989e1b484ea5bfeb540bc96758bed5


Project: http://git-wip-us.apache.org/repos/asf/predictionio-site/repo
Commit:
http://git-wip-us.apache.org/repos/asf/predictionio-site/commit/107116dc
Tree: http://git-wip-us.apache.org/repos/asf/predictionio-site/tree/107116dc
Diff: http://git-wip-us.apache.org/repos/asf/predictionio-site/diff/107116dc

Branch: refs/heads/asf-site
Commit: 107116dc22c9d6c5467ba0c1506c61b6a9e10e32
Parents: c17b960
Author: jenkins 
Authored: Fri Aug 24 17:33:22 2018 +
Committer: jenkins 
Committed: Fri Aug 24 17:33:22 2018 +

--
datacollection/batchimport/index.html | 4 +-
datacollection/channel/index.html | 6 +-
datacollection/eventapi/index.html | 20 +-
gallery/template-gallery/index.html | 2 +-
gallery/templates.yaml | 14 +
samples/tabs/index.html | 18 +-
sitemap.xml | 260 +--
templates/classification/quickstart/index.html | 30 +--
.../complementarypurchase/quickstart/index.html | 20 +-
.../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 +-
16 files changed, 329 insertions(+), 315 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/predictionio-site/blob/107116dc/datacollection/batchimport/index.html
--
diff --git a/datacollection/batchimport/index.html
b/datacollection/batchimport/index.html
index b4c83b7..4b739a3 100644
--- a/datacollection/batchimport/index.html
+++ b/datacollection/batchimport/index.html
@@ -7,7 +7,7 @@
{"event":"rate","entityType":"user","entityId":"3","targetEntityType":"item","targetEntityId":"2","properties":{"rating":1.0},"eventTime":"2014-11-21T01:04:14.729Z"}
{"event":"buy","entityType":"user","entityId":"3","targetEntityType":"item","targetEntityId":"7","eventTime":"2014-11-21T01:04:14.735Z"}
{"event":"buy","entityType":"user","entityId":"3","targetEntityType":"item","targetEntityId":"8","eventTime":"2014-11-21T01:04:14.741Z"}
-  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 FileSome of
the Apache PredictionIO SDKs also provides FileExporter client. You may use
them to prepare the JSON file as described above. The FileExporter creates
event in the same way as EventClient except that the events are written to
a JSON file instead of being sent to EventSever. The written JSON file can
then be used by batch import. 
PHP
SDK Python SDK 
Ruby SDK Java SDK 
 (coming soon) 1
+  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 FileSome of
the Apache PredictionIO SDKs also provides FileExporter client. You may use
them to prepare the JSON file as described above. The FileExporter creates
event in the same way as EventClient except that the events are written to
a JSON file instead of being sent to EventSever. The written JSON file can
then be used by batch import. 
PHP
SDK Python SDK 
Ruby SDK Java SDK 
 (coming soon) 1
2
3
4
@@ -58,7 +58,7 @@
# close the FileExporter when finish writing all
events
exporter.close()

- (coming
soon)   
 1 (coming
soon)
+ (coming
soon)   
 1 (coming
soon)
 Import Events
from Input FileImporting events from a file can be done easily
using the command line interface. Assuming that pio be in your
search path, your App ID be 123, and the input file
my_events.json be in your current working directory:1$
pio import --appid 123 --input my_events.json
  After a brief while, the tool
should return to the console without any error. Congratulations! You have
successfully imported your events.CommunityDownloadDocsGitHubSubscribe to User
Mailing ListStackoverflowContributeContributeSource CodeBug
Trackermailto:dev-subscr...@predictionio.apache.org";
target="blank">Subscribe to Development Mailing
ListApache PredictionIO, PredictionIO, Apache, the
Apache feather logo, and the Apache PredictionIO project logo are either
registered trademarks or trademarks of The Apache Software Founda

[jira] [Commented] (PIO-158) More officially deprecate support for Scala 2.10 and Spark 1.x

2018-08-24 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/PIO-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591945#comment-16591945
 ] 

ASF GitHub Bot commented on PIO-158:


Github user dszeto commented on the issue:

https://github.com/apache/predictionio/pull/459
  
@shimamoto Good call. Those have been updated for a year already.


> More officially deprecate support for Scala 2.10 and Spark 1.x
> --
>
> Key: PIO-158
> URL: https://issues.apache.org/jira/browse/PIO-158
> Project: PredictionIO
>  Issue Type: Task
>Reporter: Takako Shimamoto
>Assignee: Takako Shimamoto
>Priority: Major
>
> https://lists.apache.org/thread.html/a5f1e7d0ae61f69ff9663ea35de42a473aab132636c280fb070e256b@%3Cdev.predictionio.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)