[jira] [Commented] (PIO-101) Document usage of Plug-in of event server and engine server
[ https://issues.apache.org/jira/browse/PIO-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190818#comment-16190818 ] Sara Asher commented on PIO-101: Thank you! [~takezoe]! > Document usage of Plug-in of event server and engine server > --- > > Key: PIO-101 > URL: https://issues.apache.org/jira/browse/PIO-101 > Project: PredictionIO > Issue Type: Task > Components: Documentation >Reporter: Kenneth Chan >Assignee: Naoki Takezoe > > see > http://mail-archives.apache.org/mod_mbox/incubator-predictionio-dev/201706.mbox/%3CCAF_HxLtEonOVALSQgrCRGXctAbL7eypxwG0ErHpaBJJym15j5Q%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PIO-127) Update documentation for release process
[ https://issues.apache.org/jira/browse/PIO-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-127: -- Assignee: Chan (was: Sara Asher) > Update documentation for release process > > > Key: PIO-127 > URL: https://issues.apache.org/jira/browse/PIO-127 > Project: PredictionIO > Issue Type: Improvement >Affects Versions: 0.13.0-incubating >Reporter: Chan >Assignee: Chan > > Update PMC.md -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PIO-126) Update install.sh to use binary release
[ https://issues.apache.org/jira/browse/PIO-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-126: -- Assignee: Chan (was: Sara Asher) > Update install.sh to use binary release > --- > > Key: PIO-126 > URL: https://issues.apache.org/jira/browse/PIO-126 > Project: PredictionIO > Issue Type: Improvement >Affects Versions: 0.13.0-incubating >Reporter: Chan >Assignee: Chan >Priority: Trivial > > From v0.12.0-incubating, PredictionIO supports binary release and users will > no longer have to call .make-distribution.sh. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PIO-127) Update documentation for release process
[ https://issues.apache.org/jira/browse/PIO-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-127: -- Assignee: Sara Asher (was: Chan) > Update documentation for release process > > > Key: PIO-127 > URL: https://issues.apache.org/jira/browse/PIO-127 > Project: PredictionIO > Issue Type: Improvement >Affects Versions: 0.13.0-incubating >Reporter: Chan >Assignee: Sara Asher > > Update PMC.md -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PIO-126) Update install.sh to use binary release
[ https://issues.apache.org/jira/browse/PIO-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-126: -- Assignee: Sara Asher (was: Chan) > Update install.sh to use binary release > --- > > Key: PIO-126 > URL: https://issues.apache.org/jira/browse/PIO-126 > Project: PredictionIO > Issue Type: Improvement >Affects Versions: 0.13.0-incubating >Reporter: Chan >Assignee: Sara Asher >Priority: Trivial > > From v0.12.0-incubating, PredictionIO supports binary release and users will > no longer have to call .make-distribution.sh. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-127) Update documentation for release process
[ https://issues.apache.org/jira/browse/PIO-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-127: --- Target Version/s: 0.13.0-incubating > Update documentation for release process > > > Key: PIO-127 > URL: https://issues.apache.org/jira/browse/PIO-127 > Project: PredictionIO > Issue Type: Improvement >Affects Versions: 0.13.0-incubating >Reporter: Chan > > Update PMC.md -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PIO-127) Update documentation for release process
[ https://issues.apache.org/jira/browse/PIO-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-127: -- Assignee: Chan > Update documentation for release process > > > Key: PIO-127 > URL: https://issues.apache.org/jira/browse/PIO-127 > Project: PredictionIO > Issue Type: Improvement >Affects Versions: 0.13.0-incubating >Reporter: Chan >Assignee: Chan > > Update PMC.md -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-126) Update install.sh to use binary release
[ https://issues.apache.org/jira/browse/PIO-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-126: --- Target Version/s: 0.13.0-incubating > Update install.sh to use binary release > --- > > Key: PIO-126 > URL: https://issues.apache.org/jira/browse/PIO-126 > Project: PredictionIO > Issue Type: Improvement >Affects Versions: 0.13.0-incubating >Reporter: Chan >Priority: Trivial > > From v0.12.0-incubating, PredictionIO supports binary release and users will > no longer have to call .make-distribution.sh. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PIO-126) Update install.sh to use binary release
[ https://issues.apache.org/jira/browse/PIO-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-126: -- Assignee: Chan > Update install.sh to use binary release > --- > > Key: PIO-126 > URL: https://issues.apache.org/jira/browse/PIO-126 > Project: PredictionIO > Issue Type: Improvement >Affects Versions: 0.13.0-incubating >Reporter: Chan >Assignee: Chan >Priority: Trivial > > From v0.12.0-incubating, PredictionIO supports binary release and users will > no longer have to call .make-distribution.sh. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-125) Spark 2.2 support
[ https://issues.apache.org/jira/browse/PIO-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-125: --- Target Version/s: 0.13.0-incubating > Spark 2.2 support > - > > Key: PIO-125 > URL: https://issues.apache.org/jira/browse/PIO-125 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Reporter: Shinsuke Sugaya >Assignee: Shinsuke Sugaya > > Add Spark 2.2 to scalaSparkDepsVersion. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PIO-124) Add support for Ruby 2.4
[ https://issues.apache.org/jira/browse/PIO-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-124: -- Assignee: Donald Szeto > Add support for Ruby 2.4 > > > Key: PIO-124 > URL: https://issues.apache.org/jira/browse/PIO-124 > Project: PredictionIO > Issue Type: Improvement > Components: Ruby SDK >Reporter: anothermh >Assignee: Donald Szeto >Priority: Minor > Labels: ruby > Original Estimate: 0h > Remaining Estimate: 0h > > Ruby 2.4 can only use the json gem if the version is 2.x or higher. The > currently released version of the PredictionIO Ruby SDK has a dependency on > json ~> 1.8. > Support for Ruby 2.4 can be had easily by relaxing the version constraint on > the json gem to allow 2.x versions that are required for Ruby 2.4, and then > switching to newer versions of rspec and webmock that work with Ruby 2.4. > There is an open pull request for this feature at > https://github.com/apache/incubator-predictionio-sdk-ruby/pull/22. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PIO-113) pridection of user who can able to give answer of posted question based on whole mysql data
[ https://issues.apache.org/jira/browse/PIO-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190405#comment-16190405 ] Sara Asher commented on PIO-113: Dipen, did Ananda's suggestion of logistic regression work for you? > pridection of user who can able to give answer of posted question based on > whole mysql data > --- > > Key: PIO-113 > URL: https://issues.apache.org/jira/browse/PIO-113 > Project: PredictionIO > Issue Type: Improvement > Components: Templates >Affects Versions: 0.11.0-incubating > Environment: Linux centos 7 64 biy >Reporter: Dipen Patel > Labels: features > Fix For: 0.13.0-incubating > > > hello.. > i am looking below feature > prediction of answer based on past user data from whole database. > So can i used any existing template or required to develop new template ? > i have find some template but i dont think it is helpful to me. > Thanks > Dipen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PIO-112) pio train command not working
[ https://issues.apache.org/jira/browse/PIO-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-112: -- Assignee: Donald Szeto > pio train command not working > -- > > Key: PIO-112 > URL: https://issues.apache.org/jira/browse/PIO-112 > Project: PredictionIO > Issue Type: Bug >Reporter: Al Costa >Assignee: Donald Szeto > > When I type *pio train* on the MyRecommendation initial test on a Centos > 6-9.el6.12.3.x86_64, java build 1.8.0_131-b11, scala 2.12.2 I get > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/home/al/predictionio/lib/spark/pio-data-hdfs-assembly-0.11.0-incubating.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/home/al/predictionio/lib/pio-assembly-0.11.0-incubating.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory] > [INFO] [Runner$] Submission command: /home/al/spark/bin/spark-submit --class > org.apache.predictionio.workflow.CreateWorkflow --jars > file:/usr/java/jdk1.8.0_131/jre/lib/postgresql-42.1.4.jar,file:/usr/java/jdk1.8.0_131/jre/lib/mysql-connector-java-5.1.43-bin.jar,file:/home/al/predictionio/MyRecommendation/target/scala-2.10/template-scala-parallel-recommendation_2.10-0.1-SNAPSHOT.jar,file:/home/al/predictionio/MyRecommendation/target/scala-2.10/template-scala-parallel-recommendation-assembly-0.1-SNAPSHOT-deps.jar,file:/home/al/predictionio/lib/spark/pio-data-hdfs-assembly-0.11.0-incubating.jar,file:/home/al/predictionio/lib/spark/pio-data-localfs-assembly-0.11.0-incubating.jar,file:/home/al/predictionio/lib/spark/pio-data-elasticsearch1-assembly-0.11.0-incubating.jar,file:/home/al/predictionio/lib/spark/pio-data-jdbc-assembly-0.11.0-incubating.jar,file:/home/al/predictionio/lib/spark/pio-data-hbase-assembly-0.11.0-incubating.jar > --files > file:/home/al/predictionio/conf/log4j.properties,file:/home/al/hadoop/etc/hadoop/core-site.xml > --driver-class-path > /home/al/predictionio/conf:/usr/java/jdk1.8.0_131/jre/lib/postgresql-42.1.4.jar:/usr/java/jdk1.8.0_131/jre/lib/mysql-connector-java-5.1.43-bin.jar:/home/al/hadoop/etc/hadoop > --driver-java-options -Dpio.log.dir=/home/al > file:/home/al/predictionio/lib/pio-assembly-0.11.0-incubating.jar --engine-id > org.example.recommendation.RecommendationEngine --engine-version > 202579ebeda20d955216756ce7fd3751be7a1c5a --engine-variant > file:/home/al/predictionio/MyRecommendation/engine.json --verbosity 0 > --json-extractor Both --env > PIO_ENV_LOADED=1,PIO_STORAGE_SOURCES_MYSQL_PASSWORD=pio,PIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_meta,PIO_FS_BASEDIR=/home/al/.pio_store,PIO_STORAGE_SOURCES_MYSQL_URL=jdbc:mysql://localhost/pio,PIO_HOME=/home/al/predictionio,PIO_FS_ENGINESDIR=/home/al/.pio_store/engines,PIO_STORAGE_SOURCES_PGSQL_URL=jdbc:postgresql://localhost/pio,PIO_STORAGE_SOURCES_MYSQL_TYPE=jdbc,PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=PGSQL,PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=PGSQL,PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event,PIO_STORAGE_SOURCES_MYSQL_USERNAME=pio,PIO_STORAGE_SOURCES_PGSQL_PASSWORD=pio,PIO_STORAGE_SOURCES_PGSQL_TYPE=jdbc,PIO_FS_TMPDIR=/home/al/.pio_store/tmp,PIO_STORAGE_SOURCES_PGSQL_USERNAME=pio,PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model,PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=PGSQL,PIO_CONF_DIR=/home/al/predictionio/conf > Exception in thread "main" java.lang.NoSuchMethodError: > scala.reflect.api.JavaUniverse.runtimeMirror(Ljava/lang/ClassLoader;)Lscala/reflect/api/JavaMirrors$JavaMirror; > at > org.apache.predictionio.workflow.WorkflowUtils$.getEngine(WorkflowUtils.scala:54) > at > org.apache.predictionio.workflow.CreateWorkflow$.liftedTree1$1(CreateWorkflow.scala:196) > at > org.apache.predictionio.workflow.CreateWorkflow$.main(CreateWorkflow.scala:195) > at > org.apache.predictionio.workflow.CreateWorkflow.main(CreateWorkflow.scala) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:743) > at > org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:187) > at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:212) > at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:126) > at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala) -- This message was sent by Atlassian JIRA
[jira] [Commented] (PIO-103) Document deploying multiple engine variants
[ https://issues.apache.org/jira/browse/PIO-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190398#comment-16190398 ] Sara Asher commented on PIO-103: [~k4hoo] - do you have an example in mind? If so, is this something you can add? > Document deploying multiple engine variants > --- > > Key: PIO-103 > URL: https://issues.apache.org/jira/browse/PIO-103 > Project: PredictionIO > Issue Type: Task > Components: Documentation >Reporter: Kenneth Chan > > Add explanation, tutorial and example of how to deploy multiple engine > variants in this page. > https://predictionio.incubator.apache.org/deploy/enginevariants/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PIO-101) Document usage of Plug-in of event server and engine server
[ https://issues.apache.org/jira/browse/PIO-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190394#comment-16190394 ] Sara Asher commented on PIO-101: [~takezoe] Thank you for cleaning up the plugins implementation! Would you mind updating the documentation? > Document usage of Plug-in of event server and engine server > --- > > Key: PIO-101 > URL: https://issues.apache.org/jira/browse/PIO-101 > Project: PredictionIO > Issue Type: Task > Components: Documentation >Reporter: Kenneth Chan > > see > http://mail-archives.apache.org/mod_mbox/incubator-predictionio-dev/201706.mbox/%3CCAF_HxLtEonOVALSQgrCRGXctAbL7eypxwG0ErHpaBJJym15j5Q%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-98) Issues in building Complementary Purchase Engine Template
[ https://issues.apache.org/jira/browse/PIO-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-98: -- Target Version/s: 0.13.0-incubating > Issues in building Complementary Purchase Engine Template > - > > Key: PIO-98 > URL: https://issues.apache.org/jira/browse/PIO-98 > Project: PredictionIO > Issue Type: Bug >Reporter: salil chawla > > http://predictionio.incubator.apache.org/templates/complementarypurchase/quickstart/ > doesn't get built with 0.11.0-incubating release of predictionIO. > Looks like it is pointing to the packages and classes relevant to the older > version of PredictionIO > for example, > template-scala-parallel-complementarypurchase/src/main/scala/Algorithm.scala > is importing the P2LAlgorithm class with qualified name as > io.prediction.controller.P2LAlgorithm > but ideally it should have been > org.apache.predictionio.controller.P2LAlgorithm -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PIO-96) Storage corrupted by sharing databases between engines with different storage configs
[
https://issues.apache.org/jira/browse/PIO-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190390#comment-16190390
]
Sara Asher commented on PIO-96:
---
This is issue is likely to go away with the new microservices.
> Storage corrupted by sharing databases between engines with different storage
> configs
> -
>
> Key: PIO-96
> URL: https://issues.apache.org/jira/browse/PIO-96
> Project: PredictionIO
> Issue Type: Bug
> Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>
> When getting started with PredictionIO, it's no problem to spin up an engine
> and see it work. Problems emerge when a developer tries running multiple
> engines with different storage configs on the same underlying database, such
> as:
> * a Classifier with *Postgres* meta, event, & model storage, and
> * the Universal Recommender with *Elasticsearch* meta plus *Postgres* event &
> model storage.
> The database will become corrupt because the meta tables are stored in
> different databases, but the dynamically created event & model tables may
> mistakenly share the same name, like {{pio_event_1}}.
> We are directing folks to avoid this problem with the Heroku buildpack by
> [isolating each engine's
> database|https://github.com/heroku/predictionio-buildpack/blob/master/CUSTOM.md#provision-the-database]
> and [optionally running an eventserver per
> engine|https://github.com/heroku/predictionio-buildpack/blob/master/CUSTOM.md#user-content-eventserver].
> It's still a problem with local development, though.
> It would be great if PredictionIO's management of the database schema's would
> inherently avoid such conflicts, like by using random/UUIDs for dynamically
> created table names, so that they will never conflict.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PIO-93) Oracle database supports
[ https://issues.apache.org/jira/browse/PIO-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190387#comment-16190387 ] Sara Asher commented on PIO-93: --- Hi [~liningalex]. Do you think the pull request will be ready for 0.13? > Oracle database supports > > > Key: PIO-93 > URL: https://issues.apache.org/jira/browse/PIO-93 > Project: PredictionIO > Issue Type: New Feature > Components: Core >Reporter: Lining Sun > > A pull request is created and at > https://github.com/apache/incubator-predictionio/pull/387 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-89) Add page to documentation that lists out deprecations
[ https://issues.apache.org/jira/browse/PIO-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-89: -- Priority: Major (was: Minor) > Add page to documentation that lists out deprecations > - > > Key: PIO-89 > URL: https://issues.apache.org/jira/browse/PIO-89 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher > Labels: Documentation > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-89) Add page to documentation that lists out deprecations
[ https://issues.apache.org/jira/browse/PIO-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-89: -- Target Version/s: 0.13.0-incubating > Add page to documentation that lists out deprecations > - > > Key: PIO-89 > URL: https://issues.apache.org/jira/browse/PIO-89 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher >Priority: Minor > Labels: Documentation > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PIO-89) Add page to documentation that lists out deprecations
[ https://issues.apache.org/jira/browse/PIO-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190385#comment-16190385 ] Sara Asher commented on PIO-89: --- At minimum, our release notes need a section marking deprecating and deprecated features/libraries. Documentation should have a link to the release notes as well. > Add page to documentation that lists out deprecations > - > > Key: PIO-89 > URL: https://issues.apache.org/jira/browse/PIO-89 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher >Priority: Minor > Labels: Documentation > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-89) Add page to documentation that lists out deprecations
[ https://issues.apache.org/jira/browse/PIO-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-89: -- Component/s: Documentation > Add page to documentation that lists out deprecations > - > > Key: PIO-89 > URL: https://issues.apache.org/jira/browse/PIO-89 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher >Priority: Minor > Labels: Documentation > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-89) Add page to documentation that lists out deprecations
[ https://issues.apache.org/jira/browse/PIO-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-89: -- Labels: Documentation (was: ) > Add page to documentation that lists out deprecations > - > > Key: PIO-89 > URL: https://issues.apache.org/jira/browse/PIO-89 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher >Priority: Minor > Labels: Documentation > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-82) Improve debugging experience in IntelliJ/Eclipse when developing templates
[ https://issues.apache.org/jira/browse/PIO-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-82: -- Target Version/s: Future (was: 0.12.0-incubating) > Improve debugging experience in IntelliJ/Eclipse when developing templates > --- > > Key: PIO-82 > URL: https://issues.apache.org/jira/browse/PIO-82 > Project: PredictionIO > Issue Type: Improvement >Reporter: Sara Asher > > From Pat: Make debugging templates with IntelliJ or Eclipse much easier. This > may be helped by #1 above but perhaps also by doing refactoring of the CLI > layers. This is the single worst roadblock to getting templates developed. I > figured it out (with Donald) and documented it once upon a time but things > you do, like changing the build.sbt or other things, can wipe out the config > that was working, causing you to start over. I suspect the somewhat odd > support for ES1 and ES5 may have complicated this. This IMO would help more > than writing templates in Java! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-85) Add a method to make engine IDs settable and used with all workflow phases
[ https://issues.apache.org/jira/browse/PIO-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-85: -- Target Version/s: 0.13.0-incubating (was: 0.12.0-incubating) > Add a method to make engine IDs settable and used with all workflow phases > -- > > Key: PIO-85 > URL: https://issues.apache.org/jira/browse/PIO-85 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Reporter: Sara Asher > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-81) Remove pio build and replace with sbt targets for templates.
[ https://issues.apache.org/jira/browse/PIO-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-81: -- Priority: Minor (was: Major) > Remove pio build and replace with sbt targets for templates. > > > Key: PIO-81 > URL: https://issues.apache.org/jira/browse/PIO-81 > Project: PredictionIO > Issue Type: Improvement > Components: Build >Reporter: Sara Asher >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PIO-80) Docs on Custom Backend Support are Wrong
[ https://issues.apache.org/jira/browse/PIO-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190374#comment-16190374 ] Sara Asher commented on PIO-80: --- [~takezoe] Is this something you could take care of? > Docs on Custom Backend Support are Wrong > > > Key: PIO-80 > URL: https://issues.apache.org/jira/browse/PIO-80 > Project: PredictionIO > Issue Type: Bug > Components: Documentation >Reporter: James Ward >Priority: Minor > > The docs for Using Another Data Store - > https://predictionio.incubator.apache.org/system/anotherdatastore/ - indicate > that the custom fat jar should go into a "plugins" dir. But the contents of > that dir don't actually go into the CLASSPATH. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PIO-79) Create architecture guide for new developers
[ https://issues.apache.org/jira/browse/PIO-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-79: - Assignee: Donald Szeto > Create architecture guide for new developers > > > Key: PIO-79 > URL: https://issues.apache.org/jira/browse/PIO-79 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher >Assignee: Donald Szeto > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-79) Create architecture guide for new developers
[ https://issues.apache.org/jira/browse/PIO-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-79: -- Summary: Create architecture guide for new developers (was: Update architecture guide for new developers) > Create architecture guide for new developers > > > Key: PIO-79 > URL: https://issues.apache.org/jira/browse/PIO-79 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-79) Update architecture guide for new developers
[ https://issues.apache.org/jira/browse/PIO-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-79: -- Target Version/s: 0.13.0-incubating (was: 0.12.0-incubating) > Update architecture guide for new developers > > > Key: PIO-79 > URL: https://issues.apache.org/jira/browse/PIO-79 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-78) Modularize PIO Architecture into microservices
[ https://issues.apache.org/jira/browse/PIO-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-78: -- Labels: needsdesign (was: ) > Modularize PIO Architecture into microservices > -- > > Key: PIO-78 > URL: https://issues.apache.org/jira/browse/PIO-78 > Project: PredictionIO > Issue Type: New Feature > Components: Core >Reporter: Sara Asher > Labels: needsdesign > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-77) AWS / EMR OOTB integration
[ https://issues.apache.org/jira/browse/PIO-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-77: -- Priority: Minor (was: Major) > AWS / EMR OOTB integration > -- > > Key: PIO-77 > URL: https://issues.apache.org/jira/browse/PIO-77 > Project: PredictionIO > Issue Type: New Feature > Components: Core >Reporter: Sara Asher >Priority: Minor > Labels: needsdesign > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-77) AWS / EMR OOTB integration
[ https://issues.apache.org/jira/browse/PIO-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-77: -- Target Version/s: Future > AWS / EMR OOTB integration > -- > > Key: PIO-77 > URL: https://issues.apache.org/jira/browse/PIO-77 > Project: PredictionIO > Issue Type: New Feature > Components: Core >Reporter: Sara Asher > Labels: needsdesign > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-77) AWS / EMR OOTB integration
[ https://issues.apache.org/jira/browse/PIO-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-77: -- Labels: needsdesign (was: ) > AWS / EMR OOTB integration > -- > > Key: PIO-77 > URL: https://issues.apache.org/jira/browse/PIO-77 > Project: PredictionIO > Issue Type: New Feature > Components: Core >Reporter: Sara Asher > Labels: needsdesign > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-76) Improve installation script / process for first time users
[ https://issues.apache.org/jira/browse/PIO-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-76: -- Target Version/s: (was: 0.12.0-incubating) > Improve installation script / process for first time users > --- > > Key: PIO-76 > URL: https://issues.apache.org/jira/browse/PIO-76 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Reporter: Sara Asher >Assignee: Donald Szeto > Labels: needsdesign > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-76) Improve installation script / process for first time users
[ https://issues.apache.org/jira/browse/PIO-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-76: -- Labels: needsdesign (was: ) > Improve installation script / process for first time users > --- > > Key: PIO-76 > URL: https://issues.apache.org/jira/browse/PIO-76 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Reporter: Sara Asher >Assignee: Donald Szeto > Labels: needsdesign > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PIO-75) Improve committer documentation
[ https://issues.apache.org/jira/browse/PIO-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-75: - Assignee: Chan > Improve committer documentation > --- > > Key: PIO-75 > URL: https://issues.apache.org/jira/browse/PIO-75 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher >Assignee: Chan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-75) Improve committer documentation
[ https://issues.apache.org/jira/browse/PIO-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-75: -- Target Version/s: 0.13.0-incubating > Improve committer documentation > --- > > Key: PIO-75 > URL: https://issues.apache.org/jira/browse/PIO-75 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-74) Document release schedule for PIO
[ https://issues.apache.org/jira/browse/PIO-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-74: -- Fix Version/s: 0.12.0-incubating > Document release schedule for PIO > - > > Key: PIO-74 > URL: https://issues.apache.org/jira/browse/PIO-74 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher > Fix For: 0.12.0-incubating > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-73) Move to documentation system that has versioning (.11,.12, etc)
[ https://issues.apache.org/jira/browse/PIO-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-73: -- Priority: Minor (was: Major) > Move to documentation system that has versioning (.11,.12, etc) > --- > > Key: PIO-73 > URL: https://issues.apache.org/jira/browse/PIO-73 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (PIO-68) Port UR template to Java
[ https://issues.apache.org/jira/browse/PIO-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher closed PIO-68. - Resolution: Fixed > Port UR template to Java > > > Key: PIO-68 > URL: https://issues.apache.org/jira/browse/PIO-68 > Project: PredictionIO > Issue Type: New Feature > Components: Templates >Reporter: Sara Asher >Assignee: Donald Szeto > Fix For: 0.12.0-incubating > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-68) Port UR template to Java
[ https://issues.apache.org/jira/browse/PIO-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-68: -- Fix Version/s: 0.12.0-incubating > Port UR template to Java > > > Key: PIO-68 > URL: https://issues.apache.org/jira/browse/PIO-68 > Project: PredictionIO > Issue Type: New Feature > Components: Templates >Reporter: Sara Asher >Assignee: Donald Szeto > Fix For: 0.12.0-incubating > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-67) Create guide for creating java templates and add to documentation
[ https://issues.apache.org/jira/browse/PIO-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-67: -- Summary: Create guide for creating java templates and add to documentation (was: Add link for guide for creating java templates to documentation) > Create guide for creating java templates and add to documentation > -- > > Key: PIO-67 > URL: https://issues.apache.org/jira/browse/PIO-67 > Project: PredictionIO > Issue Type: Task > Components: Documentation >Reporter: Sara Asher >Priority: Minor > Labels: newbie > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PIO-38) add Apache Parquet as a data source
[ https://issues.apache.org/jira/browse/PIO-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172396#comment-16172396 ] Sara Asher commented on PIO-38: --- We can close this when PIO-71 is done > add Apache Parquet as a data source > --- > > Key: PIO-38 > URL: https://issues.apache.org/jira/browse/PIO-38 > Project: PredictionIO > Issue Type: New Feature > Components: Core >Reporter: Wojciech Indyk > Labels: features > > Apache Parquet (https://parquet.apache.org/) is a columnar data store, native > for Apache Spark and very well suited to storing batch data (as an input) for > PredictionIO Engine. > Parquet is very popular to archive clickstream, so it would enable to use > PredictionIO without additional import of data (and duplication) to HBase. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PIO-32) create component upgrade releases
[ https://issues.apache.org/jira/browse/PIO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172386#comment-16172386 ] Sara Asher commented on PIO-32: --- Hi [~pferrel]. I assume we can close this now? > create component upgrade releases > - > > Key: PIO-32 > URL: https://issues.apache.org/jira/browse/PIO-32 > Project: PredictionIO > Issue Type: New Feature > Components: Core >Reporter: Pat Ferrel > Labels: gsoc2017 > > Create a method for component upgrades that break binary compatibility like > Spark 2.x, Scala 2.11, and those that require source changes like > Elasticsearch 2.x > If not 2 release branches then someone needs to propose an alternative. Maven > profiles would still require different versions of PIO source to be used for > ES 2.x--not sure about other upgrades. Profiles are fine for different > dependency libs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (PIO-64) JDBCPEvents unit tests fail intermittently
[
https://issues.apache.org/jira/browse/PIO-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sara Asher resolved PIO-64.
---
Resolution: Fixed
Fix Version/s: 0.12.0-incubating
> JDBCPEvents unit tests fail intermittently
> --
>
> Key: PIO-64
> URL: https://issues.apache.org/jira/browse/PIO-64
> Project: PredictionIO
> Issue Type: Bug
>Affects Versions: 0.11.0-incubating
> Environment: Travis CI
>Reporter: Donald Szeto
>Assignee: Takako Shimamoto
> Labels: newbie
> Fix For: 0.12.0-incubating
>
>
> The creation timestamp of a test event mismatch the expectation by 1
> millisecond and sometimes causes annoyance with PR's tests not passing even
> though the error is irrelevant.
> Example test failure:
> https://travis-ci.org/apache/incubator-predictionio/jobs/228316305
> Excerpt of output above:
> {code}
> [info] PEventsSpec
> [info]
> [info] PredictionIO Storage PEvents Specification
> [info]
> [info] PEvents can be implemented by:
> [info] - JDBCPEvents
> [info]
> [info] JDBCPEvents should
> [info] - behave like any PEvents implementation
> [info]
> [info] + - (init test)
> [info] + - (insert test events)
> [info] + find in default
> [info] + find in channel
> [info] + aggregate user properties in default
> [info] + aggregate user properties in channel
> [info] + write to default
> [info] x write to channel
> [error]
> List(Event(id=None,event=$set,eType=user,eId=u3,tType=None,tId=None,p=DataMap(Map(a
> -> JInt(22), b -> JString(value13), d -> JArray(List(JInt(5), JInt(6),
> JInt(1),t=1970-01-01T01:49:03.410Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.170Z),
>
> Event(id=None,event=$unset,eType=user,eId=u3,tType=None,tId=None,p=DataMap(Map(a
> ->
> JNull)),t=1970-01-02T01:49:03.410Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.170Z),
>
> Event(id=None,event=$set,eType=user,eId=u3,tType=None,tId=None,p=DataMap(Map(b
> -> JString(value10), f -> JString(new12), d -> JArray(List(JInt(1), JInt(3),
> JInt(2),t=1970-01-03T01:49:03.410Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.170Z),
>
> Event(id=None,event=my_event3,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(propA
> -> JDouble(1.2345), propB ->
> JString(valueB))),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=Some(my_prid),ct=2017-05-03T12:43:42.172Z),
>
> Event(id=None,event=my_event4,eType=my_entity_type4,eId=my_entity_id4,tType=Some(my_target_entity_type4),tId=Some(my_target_entity_id4),p=DataMap(Map(prop6
> -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a),
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true),
> prop3 -> JArray(List(JInt(1), JInt(2),
> JInt(3),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.172Z),
>
> Event(id=None,event=my_event6,eType=my_entity_type6,eId=my_entity_id6,tType=Some(my_target_entity_type6),tId=Some(my_target_entity_id6),p=DataMap(Map(prop6
> -> JDouble(4.56), prop1 -> JInt(6), prop5 -> JArray(List(JString(a),
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true),
> prop3 -> JArray(List(JInt(6), JInt(7),
> JInt(8),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.172Z),
>
> Event(id=None,event=my_event,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(prop6
> -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a),
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true),
> prop3 -> JArray(List(JInt(1), JInt(2),
> JInt(3),t=2017-05-03T12:43:42.171Z,tags=List(),pKey=Some(my_prid),ct=2017-05-03T12:43:42.171Z),
>
> Event(id=None,event=my_event5,eType=my_entity_type5,eId=my_entity_id5,tType=Some(my_target_entity_type5),tId=Some(my_target_entity_id5),p=DataMap(Map(prop6
> -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a),
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true),
> prop3 -> JArray(List(JInt(1), JInt(2),
> JInt(3),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.172Z))
> [error]is missing:
> Event(id=None,event=my_event,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(prop6
> -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a),
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true),
> prop3 -> JArray(List(JInt(1), JInt(2),
> JInt(3),t=2017-05-03T12:43:42.171Z,tags=List(),pKey=Some(my_prid),ct=2017-05-03T12:43:42.172Z)
> [error]must not contain:
>
[jira] [Assigned] (PIO-60) Fix minor issues with author information
[ https://issues.apache.org/jira/browse/PIO-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-60: - Assignee: Chan > Fix minor issues with author information > > > Key: PIO-60 > URL: https://issues.apache.org/jira/browse/PIO-60 > Project: PredictionIO > Issue Type: Improvement >Reporter: Donald Szeto >Assignee: Chan >Priority: Minor > > Justin Mclean has pointed out a couple minor issues regarding source files in > the release: > https://lists.apache.org/thread.html/198e33ae11343da7f29257293e90ace6cae07766045240d2981efb49@%3Cgeneral.incubator.apache.org%3E > This should be fixed in the next patch release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (PIO-63) Fix incubator branding issues
[
https://issues.apache.org/jira/browse/PIO-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sara Asher reassigned PIO-63:
-
Assignee: Donald Szeto
> Fix incubator branding issues
> -
>
> Key: PIO-63
> URL: https://issues.apache.org/jira/browse/PIO-63
> Project: PredictionIO
> Issue Type: Bug
>Affects Versions: 0.11.0-incubating
>Reporter: Donald Szeto
>Assignee: Donald Szeto
>
> {quote}
> John D. Ament
> Please review the branding guide here:
> http://incubator.apache.org/guides/branding.html
> Specifically, we expect all podlings to show a logo (the actual logo has
> changed) for the Incubator, and include a disclaimer (the same release
> disclaimer) on the website. I can find neither on your website.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (PIO-62) Investigate RAT issues and other authorship information
[
https://issues.apache.org/jira/browse/PIO-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sara Asher reassigned PIO-62:
-
Assignee: Chan
> Investigate RAT issues and other authorship information
> ---
>
> Key: PIO-62
> URL: https://issues.apache.org/jira/browse/PIO-62
> Project: PredictionIO
> Issue Type: Bug
>Affects Versions: 0.11.0-incubating
>Reporter: Donald Szeto
>Assignee: Chan
> Labels: newbie
>
> {quote}
> From: Luciano Resende
> Subject: Re: [VOTE] Release Apache PredictionIO 0.11.0 (incubating) RC2
> Date: 2017-04-17 13:29 (-0700)
> List: gene...@incubator.apache.org
> show/hide original text
> I was running RAT on the source distribution and there are a lot of unknown
> licenses, some might be ok, but many are not, such as:
> *.sbt in projects and sub-projects
> *.css in docs
> Other things like signatures, etc seems ok
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
> {quote}
> Also take a look at
> # docs/manual/source/humans.txt
> #
> examples/scala-parallel-recommendation/custom-query/data/src/main/scala/org/template/recommendation/ImportDataScript.scala
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (PIO-87) Fix doc licensing issues
[ https://issues.apache.org/jira/browse/PIO-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039683#comment-16039683 ] Sara Asher commented on PIO-87: --- Hi [~pferrel]. Is this just PIO-60, PIO-62 and PIO-63? If so, I'll close this story out as a duplicate. > Fix doc licensing issues > > > Key: PIO-87 > URL: https://issues.apache.org/jira/browse/PIO-87 > Project: PredictionIO > Issue Type: Bug >Reporter: Sara Asher > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (PIO-86) Maintain a working docker container
[ https://issues.apache.org/jira/browse/PIO-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026484#comment-16026484 ] Sara Asher commented on PIO-86: --- Note from planning doc: This might be ok for experimentation but would actually get in the way of a real production level implementation, which requires docker containers for all services and not so much PIO. This features needs more clarity / discussion. For those who are interested in this feature, please provide more information in the comments! > Maintain a working docker container > --- > > Key: PIO-86 > URL: https://issues.apache.org/jira/browse/PIO-86 > Project: PredictionIO > Issue Type: Wish >Reporter: Sara Asher > Labels: needs-discussion > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (PIO-72) In `pio-shell` jdbc.StorageClient cannot be loaded
[
https://issues.apache.org/jira/browse/PIO-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sara Asher reassigned PIO-72:
-
Assignee: Sara Asher (was: Chan)
> In `pio-shell` jdbc.StorageClient cannot be loaded
> --
>
> Key: PIO-72
> URL: https://issues.apache.org/jira/browse/PIO-72
> Project: PredictionIO
> Issue Type: Bug
> Components: Core
>Affects Versions: 0.11.0-incubating
> Environment: local developer machines
>Reporter: Mars Hall
>Assignee: Sara Asher
> Attachments: image.png
>
>
> Class loading/classpath is currently broken in {{pio-shell}}. Attached
> screenshot is the public docs that explain the intended functionality.
> Instead, users see errors when attempting to use storage classes:
> {code:title=pio-shell.error|borderStyle=solid}
> java.lang.ClassNotFoundException: jdbc.StorageClient
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.apache.predictionio.data.storage.Storage$.getClient(Storage.scala:228)
> at
> org.apache.predictionio.data.storage.Storage$.org$apache$predictionio$data$storage$Storage$$updateS2CM(Storage.scala:254)
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$sourcesToClientMeta$1.apply(Storage.scala:215)
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$sourcesToClientMeta$1.apply(Storage.scala:215)
> at scala.collection.mutable.MapLike$class.getOrElseUpdate(MapLike.scala:189)
> at scala.collection.mutable.AbstractMap.getOrElseUpdate(Map.scala:91)
> at
> org.apache.predictionio.data.storage.Storage$.sourcesToClientMeta(Storage.scala:215)
> at
> org.apache.predictionio.data.storage.Storage$.getDataObject(Storage.scala:284)
> at
> org.apache.predictionio.data.storage.Storage$.getDataObjectFromRepo(Storage.scala:269)
> at
> org.apache.predictionio.data.storage.Storage$.getMetaDataApps(Storage.scala:387)
> at
> org.apache.predictionio.data.store.Common$.appsDb$lzycompute(Common.scala:27)
> at org.apache.predictionio.data.store.Common$.appsDb(Common.scala:27)
> at org.apache.predictionio.data.store.Common$.appNameToId(Common.scala:32)
> at
> org.apache.predictionio.data.store.PEventStore$.aggregateProperties(PEventStore.scala:108)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:31)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:36)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:38)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC.(:40)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC.(:42)
> at $line20.$read$$iwC$$iwC$$iwC.(:44)
> at $line20.$read$$iwC$$iwC.(:46)
> at $line20.$read$$iwC.(:48)
> at $line20.$read.(:50)
> at $line20.$read$.(:54)
> at $line20.$read$.()
> at $line20.$eval$.(:7)
> at $line20.$eval$.()
> at $line20.$eval.$print()
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.spark.repl.SparkIMain$ReadEvalPrint.call(SparkIMain.scala:1065)
> at org.apache.spark.repl.SparkIMain$Request.loadAndRun(SparkIMain.scala:1346)
> at org.apache.spark.repl.SparkIMain.loadAndRunReq$1(SparkIMain.scala:840)
> at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:871)
> at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:819)
> at org.apache.spark.repl.SparkILoop.reallyInterpret$1(SparkILoop.scala:857)
> at
> org.apache.spark.repl.SparkILoop.interpretStartingWith(SparkILoop.scala:902)
> at org.apache.spark.repl.SparkILoop.command(SparkILoop.scala:814)
> at org.apache.spark.repl.SparkILoop.processLine$1(SparkILoop.scala:657)
> at org.apache.spark.repl.SparkILoop.innerLoop$1(SparkILoop.scala:665)
> at
> org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$loop(SparkILoop.scala:670)
> at
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply$mcZ$sp(SparkILoop.scala:997)
> at
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:945)
> at
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:945)
> at
> scala.tools.nsc.util.ScalaClassLoader$.savingContextLoader(ScalaClassLoader.scala:135)
> at
> org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$process(SparkILoop.scala:945)
> at org.apache.spark.repl.SparkILoop.process(SparkILoop.scala:1059)
> at org.apache.spark.repl.Main$.main(Main.scala:31)
> at
[jira] [Assigned] (PIO-72) In `pio-shell` jdbc.StorageClient cannot be loaded
[
https://issues.apache.org/jira/browse/PIO-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sara Asher reassigned PIO-72:
-
Assignee: Chan (was: Sara Asher)
> In `pio-shell` jdbc.StorageClient cannot be loaded
> --
>
> Key: PIO-72
> URL: https://issues.apache.org/jira/browse/PIO-72
> Project: PredictionIO
> Issue Type: Bug
> Components: Core
>Affects Versions: 0.11.0-incubating
> Environment: local developer machines
>Reporter: Mars Hall
>Assignee: Chan
> Attachments: image.png
>
>
> Class loading/classpath is currently broken in {{pio-shell}}. Attached
> screenshot is the public docs that explain the intended functionality.
> Instead, users see errors when attempting to use storage classes:
> {code:title=pio-shell.error|borderStyle=solid}
> java.lang.ClassNotFoundException: jdbc.StorageClient
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.apache.predictionio.data.storage.Storage$.getClient(Storage.scala:228)
> at
> org.apache.predictionio.data.storage.Storage$.org$apache$predictionio$data$storage$Storage$$updateS2CM(Storage.scala:254)
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$sourcesToClientMeta$1.apply(Storage.scala:215)
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$sourcesToClientMeta$1.apply(Storage.scala:215)
> at scala.collection.mutable.MapLike$class.getOrElseUpdate(MapLike.scala:189)
> at scala.collection.mutable.AbstractMap.getOrElseUpdate(Map.scala:91)
> at
> org.apache.predictionio.data.storage.Storage$.sourcesToClientMeta(Storage.scala:215)
> at
> org.apache.predictionio.data.storage.Storage$.getDataObject(Storage.scala:284)
> at
> org.apache.predictionio.data.storage.Storage$.getDataObjectFromRepo(Storage.scala:269)
> at
> org.apache.predictionio.data.storage.Storage$.getMetaDataApps(Storage.scala:387)
> at
> org.apache.predictionio.data.store.Common$.appsDb$lzycompute(Common.scala:27)
> at org.apache.predictionio.data.store.Common$.appsDb(Common.scala:27)
> at org.apache.predictionio.data.store.Common$.appNameToId(Common.scala:32)
> at
> org.apache.predictionio.data.store.PEventStore$.aggregateProperties(PEventStore.scala:108)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:31)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:36)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:38)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC.(:40)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC.(:42)
> at $line20.$read$$iwC$$iwC$$iwC.(:44)
> at $line20.$read$$iwC$$iwC.(:46)
> at $line20.$read$$iwC.(:48)
> at $line20.$read.(:50)
> at $line20.$read$.(:54)
> at $line20.$read$.()
> at $line20.$eval$.(:7)
> at $line20.$eval$.()
> at $line20.$eval.$print()
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.spark.repl.SparkIMain$ReadEvalPrint.call(SparkIMain.scala:1065)
> at org.apache.spark.repl.SparkIMain$Request.loadAndRun(SparkIMain.scala:1346)
> at org.apache.spark.repl.SparkIMain.loadAndRunReq$1(SparkIMain.scala:840)
> at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:871)
> at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:819)
> at org.apache.spark.repl.SparkILoop.reallyInterpret$1(SparkILoop.scala:857)
> at
> org.apache.spark.repl.SparkILoop.interpretStartingWith(SparkILoop.scala:902)
> at org.apache.spark.repl.SparkILoop.command(SparkILoop.scala:814)
> at org.apache.spark.repl.SparkILoop.processLine$1(SparkILoop.scala:657)
> at org.apache.spark.repl.SparkILoop.innerLoop$1(SparkILoop.scala:665)
> at
> org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$loop(SparkILoop.scala:670)
> at
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply$mcZ$sp(SparkILoop.scala:997)
> at
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:945)
> at
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:945)
> at
> scala.tools.nsc.util.ScalaClassLoader$.savingContextLoader(ScalaClassLoader.scala:135)
> at
> org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$process(SparkILoop.scala:945)
> at org.apache.spark.repl.SparkILoop.process(SparkILoop.scala:1059)
> at org.apache.spark.repl.Main$.main(Main.scala:31)
> at
[jira] [Assigned] (PIO-72) In `pio-shell` jdbc.StorageClient cannot be loaded
[
https://issues.apache.org/jira/browse/PIO-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sara Asher reassigned PIO-72:
-
Assignee: Chan
> In `pio-shell` jdbc.StorageClient cannot be loaded
> --
>
> Key: PIO-72
> URL: https://issues.apache.org/jira/browse/PIO-72
> Project: PredictionIO
> Issue Type: Bug
> Components: Core
>Affects Versions: 0.11.0-incubating
> Environment: local developer machines
>Reporter: Mars Hall
>Assignee: Chan
> Attachments: image.png
>
>
> Class loading/classpath is currently broken in {{pio-shell}}. Attached
> screenshot is the public docs that explain the intended functionality.
> Instead, users see errors when attempting to use storage classes:
> {code:title=pio-shell.error|borderStyle=solid}
> java.lang.ClassNotFoundException: jdbc.StorageClient
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.apache.predictionio.data.storage.Storage$.getClient(Storage.scala:228)
> at
> org.apache.predictionio.data.storage.Storage$.org$apache$predictionio$data$storage$Storage$$updateS2CM(Storage.scala:254)
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$sourcesToClientMeta$1.apply(Storage.scala:215)
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$sourcesToClientMeta$1.apply(Storage.scala:215)
> at scala.collection.mutable.MapLike$class.getOrElseUpdate(MapLike.scala:189)
> at scala.collection.mutable.AbstractMap.getOrElseUpdate(Map.scala:91)
> at
> org.apache.predictionio.data.storage.Storage$.sourcesToClientMeta(Storage.scala:215)
> at
> org.apache.predictionio.data.storage.Storage$.getDataObject(Storage.scala:284)
> at
> org.apache.predictionio.data.storage.Storage$.getDataObjectFromRepo(Storage.scala:269)
> at
> org.apache.predictionio.data.storage.Storage$.getMetaDataApps(Storage.scala:387)
> at
> org.apache.predictionio.data.store.Common$.appsDb$lzycompute(Common.scala:27)
> at org.apache.predictionio.data.store.Common$.appsDb(Common.scala:27)
> at org.apache.predictionio.data.store.Common$.appNameToId(Common.scala:32)
> at
> org.apache.predictionio.data.store.PEventStore$.aggregateProperties(PEventStore.scala:108)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:31)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:36)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:38)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC$$iwC.(:40)
> at $line20.$read$$iwC$$iwC$$iwC$$iwC.(:42)
> at $line20.$read$$iwC$$iwC$$iwC.(:44)
> at $line20.$read$$iwC$$iwC.(:46)
> at $line20.$read$$iwC.(:48)
> at $line20.$read.(:50)
> at $line20.$read$.(:54)
> at $line20.$read$.()
> at $line20.$eval$.(:7)
> at $line20.$eval$.()
> at $line20.$eval.$print()
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.spark.repl.SparkIMain$ReadEvalPrint.call(SparkIMain.scala:1065)
> at org.apache.spark.repl.SparkIMain$Request.loadAndRun(SparkIMain.scala:1346)
> at org.apache.spark.repl.SparkIMain.loadAndRunReq$1(SparkIMain.scala:840)
> at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:871)
> at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:819)
> at org.apache.spark.repl.SparkILoop.reallyInterpret$1(SparkILoop.scala:857)
> at
> org.apache.spark.repl.SparkILoop.interpretStartingWith(SparkILoop.scala:902)
> at org.apache.spark.repl.SparkILoop.command(SparkILoop.scala:814)
> at org.apache.spark.repl.SparkILoop.processLine$1(SparkILoop.scala:657)
> at org.apache.spark.repl.SparkILoop.innerLoop$1(SparkILoop.scala:665)
> at
> org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$loop(SparkILoop.scala:670)
> at
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply$mcZ$sp(SparkILoop.scala:997)
> at
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:945)
> at
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:945)
> at
> scala.tools.nsc.util.ScalaClassLoader$.savingContextLoader(ScalaClassLoader.scala:135)
> at
> org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$process(SparkILoop.scala:945)
> at org.apache.spark.repl.SparkILoop.process(SparkILoop.scala:1059)
> at org.apache.spark.repl.Main$.main(Main.scala:31)
> at org.apache.spark.repl.Main.main(Main.scala)
> at
[jira] [Updated] (PIO-86) Maintain a working docker container
[ https://issues.apache.org/jira/browse/PIO-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-86: -- Target Version/s: 0.12.0-incubating > Maintain a working docker container > --- > > Key: PIO-86 > URL: https://issues.apache.org/jira/browse/PIO-86 > Project: PredictionIO > Issue Type: Wish >Reporter: Sara Asher > Labels: needs-discussion > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-69) Create binary version of PredictionIO as part of release process
[ https://issues.apache.org/jira/browse/PIO-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-69: -- Target Version/s: 0.12.0-incubating > Create binary version of PredictionIO as part of release process > > > Key: PIO-69 > URL: https://issues.apache.org/jira/browse/PIO-69 > Project: PredictionIO > Issue Type: New Feature > Components: Build >Reporter: Sara Asher > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-88) Scripts for Windows
[ https://issues.apache.org/jira/browse/PIO-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-88: -- Description: Create scripts so that windows users can download and install PredictionIO on their windows machines. > Scripts for Windows > --- > > Key: PIO-88 > URL: https://issues.apache.org/jira/browse/PIO-88 > Project: PredictionIO > Issue Type: New Feature >Reporter: Sara Asher > Labels: newbie > > Create scripts so that windows users can download and install PredictionIO on > their windows machines. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-88) Scripts for Windows
[ https://issues.apache.org/jira/browse/PIO-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-88: -- Labels: newbie (was: ) > Scripts for Windows > --- > > Key: PIO-88 > URL: https://issues.apache.org/jira/browse/PIO-88 > Project: PredictionIO > Issue Type: New Feature >Reporter: Sara Asher > Labels: newbie > > Create scripts so that windows users can download and install PredictionIO on > their windows machines. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-88) Scripts for Windows
Sara Asher created PIO-88: - Summary: Scripts for Windows Key: PIO-88 URL: https://issues.apache.org/jira/browse/PIO-88 Project: PredictionIO Issue Type: New Feature Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (PIO-87) Fix doc licensing issues
[ https://issues.apache.org/jira/browse/PIO-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025808#comment-16025808 ] Sara Asher commented on PIO-87: --- [~pferrel] Can you list out what the licensing issues are? > Fix doc licensing issues > > > Key: PIO-87 > URL: https://issues.apache.org/jira/browse/PIO-87 > Project: PredictionIO > Issue Type: Bug >Reporter: Sara Asher > Fix For: 0.12.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-87) Fix doc licensing issues
Sara Asher created PIO-87: - Summary: Fix doc licensing issues Key: PIO-87 URL: https://issues.apache.org/jira/browse/PIO-87 Project: PredictionIO Issue Type: Bug Reporter: Sara Asher Fix For: 0.12.0-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-86) Maintain a working docker container
Sara Asher created PIO-86: - Summary: Maintain a working docker container Key: PIO-86 URL: https://issues.apache.org/jira/browse/PIO-86 Project: PredictionIO Issue Type: Wish Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-85) Add a method to make engine IDs settable and used with all workflow phases
Sara Asher created PIO-85: - Summary: Add a method to make engine IDs settable and used with all workflow phases Key: PIO-85 URL: https://issues.apache.org/jira/browse/PIO-85 Project: PredictionIO Issue Type: Improvement Components: Core Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-81) Remove pio build and replace with sbt targets for templates.
[ https://issues.apache.org/jira/browse/PIO-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-81: -- Issue Type: Improvement (was: Bug) > Remove pio build and replace with sbt targets for templates. > > > Key: PIO-81 > URL: https://issues.apache.org/jira/browse/PIO-81 > Project: PredictionIO > Issue Type: Improvement > Components: Build >Reporter: Sara Asher > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-82) Improve debugging experience in IntelliJ/Eclipse when developing templates
[ https://issues.apache.org/jira/browse/PIO-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-82: -- Issue Type: Improvement (was: Bug) > Improve debugging experience in IntelliJ/Eclipse when developing templates > --- > > Key: PIO-82 > URL: https://issues.apache.org/jira/browse/PIO-82 > Project: PredictionIO > Issue Type: Improvement >Reporter: Sara Asher > > From Pat: Make debugging templates with IntelliJ or Eclipse much easier. This > may be helped by #1 above but perhaps also by doing refactoring of the CLI > layers. This is the single worst roadblock to getting templates developed. I > figured it out (with Donald) and documented it once upon a time but things > you do, like changing the build.sbt or other things, can wipe out the config > that was working, causing you to start over. I suspect the somewhat odd > support for ES1 and ES5 may have complicated this. This IMO would help more > than writing templates in Java! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-82) Improve debugging experience in IntelliJ/Eclipse when developing templates
Sara Asher created PIO-82: - Summary: Improve debugging experience in IntelliJ/Eclipse when developing templates Key: PIO-82 URL: https://issues.apache.org/jira/browse/PIO-82 Project: PredictionIO Issue Type: Bug Reporter: Sara Asher >From Pat: Make debugging templates with IntelliJ or Eclipse much easier. This >may be helped by #1 above but perhaps also by doing refactoring of the CLI >layers. This is the single worst roadblock to getting templates developed. I >figured it out (with Donald) and documented it once upon a time but things you >do, like changing the build.sbt or other things, can wipe out the config that >was working, causing you to start over. I suspect the somewhat odd support for >ES1 and ES5 may have complicated this. This IMO would help more than writing >templates in Java! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-81) Remove pio build and replace with sbt targets for templates.
Sara Asher created PIO-81: - Summary: Remove pio build and replace with sbt targets for templates. Key: PIO-81 URL: https://issues.apache.org/jira/browse/PIO-81 Project: PredictionIO Issue Type: Bug Components: Build Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-79) Update architecture guide for new developers
[ https://issues.apache.org/jira/browse/PIO-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-79: -- Target Version/s: 0.12.0-incubating > Update architecture guide for new developers > > > Key: PIO-79 > URL: https://issues.apache.org/jira/browse/PIO-79 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Sara Asher > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-79) Update architecture guide for new developers
Sara Asher created PIO-79: - Summary: Update architecture guide for new developers Key: PIO-79 URL: https://issues.apache.org/jira/browse/PIO-79 Project: PredictionIO Issue Type: Improvement Components: Documentation Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-78) Modularize PIO Architecture into microservices
[ https://issues.apache.org/jira/browse/PIO-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-78: -- Target Version/s: 0.13.0-incubating > Modularize PIO Architecture into microservices > -- > > Key: PIO-78 > URL: https://issues.apache.org/jira/browse/PIO-78 > Project: PredictionIO > Issue Type: New Feature > Components: Core >Reporter: Sara Asher > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-78) Modularize PIO Architecture into microservices
Sara Asher created PIO-78: - Summary: Modularize PIO Architecture into microservices Key: PIO-78 URL: https://issues.apache.org/jira/browse/PIO-78 Project: PredictionIO Issue Type: New Feature Components: Core Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-77) AWS / EMR OOTB integration
Sara Asher created PIO-77: - Summary: AWS / EMR OOTB integration Key: PIO-77 URL: https://issues.apache.org/jira/browse/PIO-77 Project: PredictionIO Issue Type: New Feature Components: Core Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-76) Improve installation script / process for first time users
Sara Asher created PIO-76: - Summary: Improve installation script / process for first time users Key: PIO-76 URL: https://issues.apache.org/jira/browse/PIO-76 Project: PredictionIO Issue Type: Improvement Components: Core Reporter: Sara Asher Assignee: Donald Szeto -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-75) Improve committer documentation
Sara Asher created PIO-75: - Summary: Improve committer documentation Key: PIO-75 URL: https://issues.apache.org/jira/browse/PIO-75 Project: PredictionIO Issue Type: Improvement Components: Documentation Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-73) Move to documentation system that has versioning (.11,.12, etc)
Sara Asher created PIO-73: - Summary: Move to documentation system that has versioning (.11,.12, etc) Key: PIO-73 URL: https://issues.apache.org/jira/browse/PIO-73 Project: PredictionIO Issue Type: Improvement Components: Documentation Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-69) Create binary version of PredictionIO as part of release process
Sara Asher created PIO-69: - Summary: Create binary version of PredictionIO as part of release process Key: PIO-69 URL: https://issues.apache.org/jira/browse/PIO-69 Project: PredictionIO Issue Type: New Feature Components: Build Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-68) Port UR template to Java
Sara Asher created PIO-68: - Summary: Port UR template to Java Key: PIO-68 URL: https://issues.apache.org/jira/browse/PIO-68 Project: PredictionIO Issue Type: New Feature Components: Templates Reporter: Sara Asher Assignee: Donald Szeto -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-67) Add link for guide for creating java templates to documentation
Sara Asher created PIO-67: - Summary: Add link for guide for creating java templates to documentation Key: PIO-67 URL: https://issues.apache.org/jira/browse/PIO-67 Project: PredictionIO Issue Type: Task Components: Documentation Reporter: Sara Asher Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-36) Use Spark standalone cluster in integration tests
[ https://issues.apache.org/jira/browse/PIO-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-36: -- Component/s: Core > Use Spark standalone cluster in integration tests > - > > Key: PIO-36 > URL: https://issues.apache.org/jira/browse/PIO-36 > Project: PredictionIO > Issue Type: Bug > Components: Core >Reporter: Marcin Ziemiński >Priority: Minor > Labels: gsoc2017 > > Although Spark master and worker are executed inside the docker image that > run integration tests, no tests actually make use of them. Only a default > local spark implementation is used. Setting a --master to a living cluster > would resemble a real world cases better and also be more reliable. > The python framework has to be updated to fix this issue, which should be > just a matter of adding a few lines. We can make it an option in the tests to > set up the master. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-29) Implement Admin Server
[ https://issues.apache.org/jira/browse/PIO-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-29: -- Component/s: Core > Implement Admin Server > -- > > Key: PIO-29 > URL: https://issues.apache.org/jira/browse/PIO-29 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Reporter: Marcin Ziemiński >Priority: Minor > Labels: gsoc2017, newbie > > Despite the fact that it is possible to start the admin server, its > implementation is lacking most of the PIO's functionality. What is there is > basically a copy of some code written in the console package. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-31) Move from spray to akka-http in servers
[ https://issues.apache.org/jira/browse/PIO-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-31: -- Labels: gsoc2017 newbie (was: gsoc2017) > Move from spray to akka-http in servers > --- > > Key: PIO-31 > URL: https://issues.apache.org/jira/browse/PIO-31 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Reporter: Marcin Ziemiński > Labels: gsoc2017, newbie > > On account of the death of spray for http and it being reborn as akka-http we > should update EventServer and Dashbord. It should be fairly simple, as > described in the following guide: > http://doc.akka.io/docs/akka/2.4/scala/http/migration-from-spray.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-31) Move from spray to akka-http in servers
[ https://issues.apache.org/jira/browse/PIO-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-31: -- Component/s: Core > Move from spray to akka-http in servers > --- > > Key: PIO-31 > URL: https://issues.apache.org/jira/browse/PIO-31 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Reporter: Marcin Ziemiński > Labels: gsoc2017, newbie > > On account of the death of spray for http and it being reborn as akka-http we > should update EventServer and Dashbord. It should be fairly simple, as > described in the following guide: > http://doc.akka.io/docs/akka/2.4/scala/http/migration-from-spray.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-29) Implement Admin Server
[ https://issues.apache.org/jira/browse/PIO-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-29: -- Labels: gsoc2017 newbie (was: gsoc2017) > Implement Admin Server > -- > > Key: PIO-29 > URL: https://issues.apache.org/jira/browse/PIO-29 > Project: PredictionIO > Issue Type: Improvement >Reporter: Marcin Ziemiński >Priority: Minor > Labels: gsoc2017, newbie > > Despite the fact that it is possible to start the admin server, its > implementation is lacking most of the PIO's functionality. What is there is > basically a copy of some code written in the console package. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-18) Documentation for setting up the project for developers
[ https://issues.apache.org/jira/browse/PIO-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-18: -- Component/s: (was: Core) Documentation > Documentation for setting up the project for developers > --- > > Key: PIO-18 > URL: https://issues.apache.org/jira/browse/PIO-18 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Hyukjin Kwon >Priority: Minor > Labels: gsoc2017 > > It seems the documentation is missing, for setting up IDE for PIO itself not > for templates. > It seem the documentation here > http://predictionio.incubator.apache.org/resources/intellij only working for > templates. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-18) Documentation for setting up the project for developers
[ https://issues.apache.org/jira/browse/PIO-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-18: -- Component/s: Core > Documentation for setting up the project for developers > --- > > Key: PIO-18 > URL: https://issues.apache.org/jira/browse/PIO-18 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Hyukjin Kwon >Priority: Minor > Labels: gsoc2017 > > It seems the documentation is missing, for setting up IDE for PIO itself not > for templates. > It seem the documentation here > http://predictionio.incubator.apache.org/resources/intellij only working for > templates. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-9) Clean up examples under examples/
[ https://issues.apache.org/jira/browse/PIO-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-9: - Labels: newbie (was: ) > Clean up examples under examples/ > - > > Key: PIO-9 > URL: https://issues.apache.org/jira/browse/PIO-9 > Project: PredictionIO > Issue Type: Improvement > Components: Templates >Reporter: Xusen Yin >Priority: Minor > Labels: newbie > > Code files under examples/ use different package names, e.g. com.test, > com.test1, org.template. We should clean the code and change them into a > unified package name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-9) Clean up examples under examples/
[ https://issues.apache.org/jira/browse/PIO-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-9: - Component/s: Templates > Clean up examples under examples/ > - > > Key: PIO-9 > URL: https://issues.apache.org/jira/browse/PIO-9 > Project: PredictionIO > Issue Type: Improvement > Components: Templates >Reporter: Xusen Yin >Priority: Minor > Labels: newbie > > Code files under examples/ use different package names, e.g. com.test, > com.test1, org.template. We should clean the code and change them into a > unified package name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-66) Document JIRA processes and add to public documentation
[ https://issues.apache.org/jira/browse/PIO-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-66: -- Target Version/s: 0.12.0-incubating Fix Version/s: (was: 0.12.0-incubating) > Document JIRA processes and add to public documentation > --- > > Key: PIO-66 > URL: https://issues.apache.org/jira/browse/PIO-66 > Project: PredictionIO > Issue Type: Task >Reporter: Sara Asher >Assignee: Sara Asher > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-38) add Apache Parquet as a data source
[ https://issues.apache.org/jira/browse/PIO-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-38: -- Component/s: Core > add Apache Parquet as a data source > --- > > Key: PIO-38 > URL: https://issues.apache.org/jira/browse/PIO-38 > Project: PredictionIO > Issue Type: New Feature > Components: Core >Reporter: Wojciech Indyk > Labels: features > > Apache Parquet (https://parquet.apache.org/) is a columnar data store, native > for Apache Spark and very well suited to storing batch data (as an input) for > PredictionIO Engine. > Parquet is very popular to archive clickstream, so it would enable to use > PredictionIO without additional import of data (and duplication) to HBase. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-56) Unit tests in module core should not require real setup
[ https://issues.apache.org/jira/browse/PIO-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-56: -- Target Version/s: 0.12.0-incubating > Unit tests in module core should not require real setup > --- > > Key: PIO-56 > URL: https://issues.apache.org/jira/browse/PIO-56 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Affects Versions: 0.10.0-incubating > Environment: Tested with Mac OS X, i7, 8GB >Reporter: Lucas Bonatto Miguel > Labels: development_environment > > *This issue affects only developers* > When downloading the code from github and trying to run the tests of the > project core via sbt, one will face an error stating that the METADATA > configuration is missing, e.g: > [ERROR] [Storage$] Required repository (METADATA) configuration is missing. > [ERROR] [Storage$] There were 1 configuration errors. Exiting. > It looks like the project predictionio core requires a METADATA datasource > (elasticsearch) installed and configured in the developer machine. > There are some benefits if the project require less external > installation/configuration: > - Developers would have an easy setup of the environment. > - Continuous integration would be easier > How to reproduce: > - Download predictionio from github > - In root folder run ./make-distribution.sh > - In root folder run sbt core/test -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-56) Unit tests in module core should not require real setup
[ https://issues.apache.org/jira/browse/PIO-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-56: -- Component/s: Core > Unit tests in module core should not require real setup > --- > > Key: PIO-56 > URL: https://issues.apache.org/jira/browse/PIO-56 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Affects Versions: 0.10.0-incubating > Environment: Tested with Mac OS X, i7, 8GB >Reporter: Lucas Bonatto Miguel > Labels: development_environment > > *This issue affects only developers* > When downloading the code from github and trying to run the tests of the > project core via sbt, one will face an error stating that the METADATA > configuration is missing, e.g: > [ERROR] [Storage$] Required repository (METADATA) configuration is missing. > [ERROR] [Storage$] There were 1 configuration errors. Exiting. > It looks like the project predictionio core requires a METADATA datasource > (elasticsearch) installed and configured in the developer machine. > There are some benefits if the project require less external > installation/configuration: > - Developers would have an easy setup of the environment. > - Continuous integration would be easier > How to reproduce: > - Download predictionio from github > - In root folder run ./make-distribution.sh > - In root folder run sbt core/test -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-60) Fix minor issues with author information
[ https://issues.apache.org/jira/browse/PIO-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-60: -- Target Version/s: 0.12.0-incubating > Fix minor issues with author information > > > Key: PIO-60 > URL: https://issues.apache.org/jira/browse/PIO-60 > Project: PredictionIO > Issue Type: Improvement >Reporter: Donald Szeto >Priority: Minor > > Justin Mclean has pointed out a couple minor issues regarding source files in > the release: > https://lists.apache.org/thread.html/198e33ae11343da7f29257293e90ace6cae07766045240d2981efb49@%3Cgeneral.incubator.apache.org%3E > This should be fixed in the next patch release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-61) Add S3 Model Data Repository
[ https://issues.apache.org/jira/browse/PIO-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-61: -- Target Version/s: 0.12.0-incubating Component/s: Core > Add S3 Model Data Repository > > > Key: PIO-61 > URL: https://issues.apache.org/jira/browse/PIO-61 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Reporter: Shinsuke Sugaya >Assignee: Shinsuke Sugaya > > To put/get model data to AWS S3 directly, using aws-java-sdk-s3, add > storage/s3 implementation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-62) Investigate RAT issues and other authorship information
[
https://issues.apache.org/jira/browse/PIO-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sara Asher updated PIO-62:
--
Target Version/s: 0.12.0-incubating
> Investigate RAT issues and other authorship information
> ---
>
> Key: PIO-62
> URL: https://issues.apache.org/jira/browse/PIO-62
> Project: PredictionIO
> Issue Type: Bug
>Affects Versions: 0.11.0-incubating
>Reporter: Donald Szeto
> Labels: newbie
>
> {quote}
> From: Luciano Resende
> Subject: Re: [VOTE] Release Apache PredictionIO 0.11.0 (incubating) RC2
> Date: 2017-04-17 13:29 (-0700)
> List: gene...@incubator.apache.org
> show/hide original text
> I was running RAT on the source distribution and there are a lot of unknown
> licenses, some might be ok, but many are not, such as:
> *.sbt in projects and sub-projects
> *.css in docs
> Other things like signatures, etc seems ok
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
> {quote}
> Also take a look at
> # docs/manual/source/humans.txt
> #
> examples/scala-parallel-recommendation/custom-query/data/src/main/scala/org/template/recommendation/ImportDataScript.scala
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (PIO-64) JDBCPEvents unit tests fail intermittently
[
https://issues.apache.org/jira/browse/PIO-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sara Asher updated PIO-64:
--
Target Version/s: 0.12.0-incubating
> JDBCPEvents unit tests fail intermittently
> --
>
> Key: PIO-64
> URL: https://issues.apache.org/jira/browse/PIO-64
> Project: PredictionIO
> Issue Type: Bug
>Affects Versions: 0.11.0-incubating
> Environment: Travis CI
>Reporter: Donald Szeto
>Assignee: Takako Shimamoto
> Labels: newbie
>
> The creation timestamp of a test event mismatch the expectation by 1
> millisecond and sometimes causes annoyance with PR's tests not passing even
> though the error is irrelevant.
> Example test failure:
> https://travis-ci.org/apache/incubator-predictionio/jobs/228316305
> Excerpt of output above:
> {code}
> [info] PEventsSpec
> [info]
> [info] PredictionIO Storage PEvents Specification
> [info]
> [info] PEvents can be implemented by:
> [info] - JDBCPEvents
> [info]
> [info] JDBCPEvents should
> [info] - behave like any PEvents implementation
> [info]
> [info] + - (init test)
> [info] + - (insert test events)
> [info] + find in default
> [info] + find in channel
> [info] + aggregate user properties in default
> [info] + aggregate user properties in channel
> [info] + write to default
> [info] x write to channel
> [error]
> List(Event(id=None,event=$set,eType=user,eId=u3,tType=None,tId=None,p=DataMap(Map(a
> -> JInt(22), b -> JString(value13), d -> JArray(List(JInt(5), JInt(6),
> JInt(1),t=1970-01-01T01:49:03.410Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.170Z),
>
> Event(id=None,event=$unset,eType=user,eId=u3,tType=None,tId=None,p=DataMap(Map(a
> ->
> JNull)),t=1970-01-02T01:49:03.410Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.170Z),
>
> Event(id=None,event=$set,eType=user,eId=u3,tType=None,tId=None,p=DataMap(Map(b
> -> JString(value10), f -> JString(new12), d -> JArray(List(JInt(1), JInt(3),
> JInt(2),t=1970-01-03T01:49:03.410Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.170Z),
>
> Event(id=None,event=my_event3,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(propA
> -> JDouble(1.2345), propB ->
> JString(valueB))),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=Some(my_prid),ct=2017-05-03T12:43:42.172Z),
>
> Event(id=None,event=my_event4,eType=my_entity_type4,eId=my_entity_id4,tType=Some(my_target_entity_type4),tId=Some(my_target_entity_id4),p=DataMap(Map(prop6
> -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a),
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true),
> prop3 -> JArray(List(JInt(1), JInt(2),
> JInt(3),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.172Z),
>
> Event(id=None,event=my_event6,eType=my_entity_type6,eId=my_entity_id6,tType=Some(my_target_entity_type6),tId=Some(my_target_entity_id6),p=DataMap(Map(prop6
> -> JDouble(4.56), prop1 -> JInt(6), prop5 -> JArray(List(JString(a),
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true),
> prop3 -> JArray(List(JInt(6), JInt(7),
> JInt(8),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.172Z),
>
> Event(id=None,event=my_event,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(prop6
> -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a),
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true),
> prop3 -> JArray(List(JInt(1), JInt(2),
> JInt(3),t=2017-05-03T12:43:42.171Z,tags=List(),pKey=Some(my_prid),ct=2017-05-03T12:43:42.171Z),
>
> Event(id=None,event=my_event5,eType=my_entity_type5,eId=my_entity_id5,tType=Some(my_target_entity_type5),tId=Some(my_target_entity_id5),p=DataMap(Map(prop6
> -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a),
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true),
> prop3 -> JArray(List(JInt(1), JInt(2),
> JInt(3),t=2017-05-03T12:43:42.172Z,tags=List(),pKey=None,ct=2017-05-03T12:43:42.172Z))
> [error]is missing:
> Event(id=None,event=my_event,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(prop6
> -> JDouble(4.56), prop1 -> JInt(1), prop5 -> JArray(List(JString(a),
> JString(b), JString(c))), prop2 -> JString(value2), prop4 -> JBool(true),
> prop3 -> JArray(List(JInt(1), JInt(2),
> JInt(3),t=2017-05-03T12:43:42.171Z,tags=List(),pKey=Some(my_prid),ct=2017-05-03T12:43:42.172Z)
> [error]must not contain:
> Event(id=None,event=my_event,eType=my_entity_type,eId=my_entity_id,tType=Some(my_target_entity_type),tId=Some(my_target_entity_id),p=DataMap(Map(prop6
>
[jira] [Updated] (PIO-63) Fix incubator branding issues
[
https://issues.apache.org/jira/browse/PIO-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sara Asher updated PIO-63:
--
Target Version/s: 0.12.0-incubating
> Fix incubator branding issues
> -
>
> Key: PIO-63
> URL: https://issues.apache.org/jira/browse/PIO-63
> Project: PredictionIO
> Issue Type: Bug
>Affects Versions: 0.11.0-incubating
>Reporter: Donald Szeto
>
> {quote}
> John D. Ament
> Please review the branding guide here:
> http://incubator.apache.org/guides/branding.html
> Specifically, we expect all podlings to show a logo (the actual logo has
> changed) for the Incubator, and include a disclaimer (the same release
> disclaimer) on the website. I can find neither on your website.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (PIO-65) Cache downloaded jars in Travis build
[ https://issues.apache.org/jira/browse/PIO-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-65: -- Target Version/s: 0.12.0-incubating > Cache downloaded jars in Travis build > - > > Key: PIO-65 > URL: https://issues.apache.org/jira/browse/PIO-65 > Project: PredictionIO > Issue Type: Task >Reporter: Naoki Takezoe >Assignee: Naoki Takezoe > > Sometimes Travis build fails in downloading jars. Now Travis build has 12 > patterns of test and we don't have a permission to rebuild failed test. So we > have to re-run all patterns by additional push or reopen pull request even if > a part of test failed. > Maybe caching them makes Travis build stable and also decreases build time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (PIO-65) Cache downloaded jars in Travis build
[ https://issues.apache.org/jira/browse/PIO-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-65: - Assignee: Sara Asher > Cache downloaded jars in Travis build > - > > Key: PIO-65 > URL: https://issues.apache.org/jira/browse/PIO-65 > Project: PredictionIO > Issue Type: Task >Reporter: Naoki Takezoe >Assignee: Sara Asher > > Sometimes Travis build fails in downloading jars. Now Travis build has 12 > patterns of test and we don't have a permission to rebuild failed test. So we > have to re-run all patterns by additional push or reopen pull request even if > a part of test failed. > Maybe caching them makes Travis build stable and also decreases build time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (PIO-65) Cache downloaded jars in Travis build
[ https://issues.apache.org/jira/browse/PIO-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-65: - Assignee: Naoki Takezoe (was: Sara Asher) > Cache downloaded jars in Travis build > - > > Key: PIO-65 > URL: https://issues.apache.org/jira/browse/PIO-65 > Project: PredictionIO > Issue Type: Task >Reporter: Naoki Takezoe >Assignee: Naoki Takezoe > > Sometimes Travis build fails in downloading jars. Now Travis build has 12 > patterns of test and we don't have a permission to rebuild failed test. So we > have to re-run all patterns by additional push or reopen pull request even if > a part of test failed. > Maybe caching them makes Travis build stable and also decreases build time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (PIO-61) Add S3 Model Data Repository
[ https://issues.apache.org/jira/browse/PIO-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher reassigned PIO-61: - Assignee: Shinsuke Sugaya (was: Sara Asher) > Add S3 Model Data Repository > > > Key: PIO-61 > URL: https://issues.apache.org/jira/browse/PIO-61 > Project: PredictionIO > Issue Type: Improvement >Reporter: Shinsuke Sugaya >Assignee: Shinsuke Sugaya > > To put/get model data to AWS S3 directly, using aws-java-sdk-s3, add > storage/s3 implementation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
