[jira] [Created] (PIO-134) Document how to upgrade from 0.11, including building 0.12 for defaults used by 0.11
Donald Szeto created PIO-134: Summary: Document how to upgrade from 0.11, including building 0.12 for defaults used by 0.11 Key: PIO-134 URL: https://issues.apache.org/jira/browse/PIO-134 Project: PredictionIO Issue Type: Improvement Components: Documentation Reporter: Donald Szeto -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (PIO-133) Make sure project web site meets all requirements in Apache Project Website Branding Policy
[ https://issues.apache.org/jira/browse/PIO-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-133. -- Resolution: Fixed > Make sure project web site meets all requirements in Apache Project Website > Branding Policy > --- > > Key: PIO-133 > URL: https://issues.apache.org/jira/browse/PIO-133 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Donald Szeto >Assignee: Donald Szeto > > Meet all requirements described in > https://www.apache.org/foundation/marks/pmcs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (PIO-133) Make sure project web site meets all requirements in Apache Project Website Branding Policy
Donald Szeto created PIO-133: Summary: Make sure project web site meets all requirements in Apache Project Website Branding Policy Key: PIO-133 URL: https://issues.apache.org/jira/browse/PIO-133 Project: PredictionIO Issue Type: Improvement Components: Documentation Reporter: Donald Szeto Assignee: Donald Szeto Meet all requirements described in https://www.apache.org/foundation/marks/pmcs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (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:all-tabpanel ] Donald Szeto closed PIO-101. Resolution: Fixed > 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] [Closed] (PIO-129) CLI document does not expand side menu
[
https://issues.apache.org/jira/browse/PIO-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto closed PIO-129.
Resolution: Fixed
> CLI document does not expand side menu
> --
>
> Key: PIO-129
> URL: https://issues.apache.org/jira/browse/PIO-129
> Project: PredictionIO
> Issue Type: Improvement
> Components: Documentation
>Reporter: Naoki Takezoe
>Assignee: Naoki Takezoe
>Priority: Minor
>
> There are links to CLI document in the deploy section and collecting data
> section of the side menu, but if these links are clicked, the side menu is
> closed because these links have a hash like {{/cli/#engine-commands}}. I
> think that such unclear navigation would confuse readers.
> https://predictionio.incubator.apache.org/cli/#engine-commands
> I propose to remove these links from the deploy section and the collecting
> data section, and put a link to CLI document in the resource section without
> hash. In addition, put links to the CLI reference in documents of the event
> server and the engine server.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (PIO-125) Spark 2.2 support
[ https://issues.apache.org/jira/browse/PIO-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-125. -- Resolution: Fixed > 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] [Closed] (PIO-131) Fix Apache licensing issues for doc site
[ https://issues.apache.org/jira/browse/PIO-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto closed PIO-131. Resolution: Fixed > Fix Apache licensing issues for doc site > > > Key: PIO-131 > URL: https://issues.apache.org/jira/browse/PIO-131 > Project: PredictionIO > Issue Type: Task >Reporter: Chan >Assignee: Chan > > Fix issues blocking graduation > (https://www.mail-archive.com/general@incubator.apache.org/msg61352.html) > 1. Add links to http://apache.org as in > https://www.apache.org/foundation/marks/pmcs#navigation > 2. Add instructions for checking signature of download as in > http://httpd.apache.org/download.cgi#verify -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (PIO-130) Remove old releases from mirrors
[ https://issues.apache.org/jira/browse/PIO-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto closed PIO-130. Resolution: Fixed > Remove old releases from mirrors > > > Key: PIO-130 > URL: https://issues.apache.org/jira/browse/PIO-130 > Project: PredictionIO > Issue Type: Task >Reporter: Donald Szeto >Assignee: Donald Szeto > > As pointed out by > https://lists.apache.org/thread.html/0f9d23328807269e984bc827d679008d257bde9b24f01e84aa2a3349@%3Cgeneral.incubator.apache.org%3E, > we need to remove old releases from mirrors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PIO-130) Remove old releases from mirrors
[ https://issues.apache.org/jira/browse/PIO-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16193666#comment-16193666 ] Donald Szeto commented on PIO-130: -- Removed 0.10.0-incubating and 0.11.0-incubating. https://dist.apache.org/repos/dist/release/incubator/predictionio/ > Remove old releases from mirrors > > > Key: PIO-130 > URL: https://issues.apache.org/jira/browse/PIO-130 > Project: PredictionIO > Issue Type: Task >Reporter: Donald Szeto >Assignee: Donald Szeto > > As pointed out by > https://lists.apache.org/thread.html/0f9d23328807269e984bc827d679008d257bde9b24f01e84aa2a3349@%3Cgeneral.incubator.apache.org%3E, > we need to remove old releases from mirrors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (PIO-132) Add instructions to verify download against signatures and hashes
[ https://issues.apache.org/jira/browse/PIO-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto closed PIO-132. Resolution: Duplicate > Add instructions to verify download against signatures and hashes > - > > Key: PIO-132 > URL: https://issues.apache.org/jira/browse/PIO-132 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Affects Versions: 0.12.0-incubating >Reporter: Donald Szeto >Assignee: Donald Szeto > > As pointed out in > https://lists.apache.org/thread.html/0f9d23328807269e984bc827d679008d257bde9b24f01e84aa2a3349@%3Cgeneral.incubator.apache.org%3E, > there should be instructions on how to verify downloads against signatures > and hashes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (PIO-132) Add instructions to verify download against signatures and hashes
Donald Szeto created PIO-132: Summary: Add instructions to verify download against signatures and hashes Key: PIO-132 URL: https://issues.apache.org/jira/browse/PIO-132 Project: PredictionIO Issue Type: Improvement Components: Documentation Affects Versions: 0.12.0-incubating Reporter: Donald Szeto Assignee: Donald Szeto As pointed out in https://lists.apache.org/thread.html/0f9d23328807269e984bc827d679008d257bde9b24f01e84aa2a3349@%3Cgeneral.incubator.apache.org%3E, there should be instructions on how to verify downloads against signatures and hashes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (PIO-130) Improve project web site to meet branding requirements
Donald Szeto created PIO-130: Summary: Improve project web site to meet branding requirements Key: PIO-130 URL: https://issues.apache.org/jira/browse/PIO-130 Project: PredictionIO Issue Type: Improvement Components: Documentation Affects Versions: 0.12.0-incubating Reporter: Donald Szeto Assignee: Donald Szeto As pointed out by https://lists.apache.org/thread.html/0f9d23328807269e984bc827d679008d257bde9b24f01e84aa2a3349@%3Cgeneral.incubator.apache.org%3E, we need to fix branding issues following https://www.apache.org/foundation/marks/pmcs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-128) Incorporate all 7 templates that are in Apache repositories
[ https://issues.apache.org/jira/browse/PIO-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-128: - Description: Current integration tests only test against a couple templates. We should expand our tests to include at least all 7 templates on ASF. Also include the universal recommender as it is the most popular template in PIO ecosystem. was:Current integration tests only test against a couple templates. We should expand our tests to include at least all 7 templates on ASF. > Incorporate all 7 templates that are in Apache repositories > --- > > Key: PIO-128 > URL: https://issues.apache.org/jira/browse/PIO-128 > Project: PredictionIO > Issue Type: Improvement > Components: Test >Reporter: Donald Szeto > > Current integration tests only test against a couple templates. We should > expand our tests to include at least all 7 templates on ASF. > Also include the universal recommender as it is the most popular template in > PIO ecosystem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (PIO-128) Incorporate all 7 templates that are in Apache repositories
Donald Szeto created PIO-128: Summary: Incorporate all 7 templates that are in Apache repositories Key: PIO-128 URL: https://issues.apache.org/jira/browse/PIO-128 Project: PredictionIO Issue Type: Improvement Components: Test Reporter: Donald Szeto Current integration tests only test against a couple templates. We should expand our tests to include at least all 7 templates on ASF. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PIO-68) Port UR template to Java
[ https://issues.apache.org/jira/browse/PIO-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172398#comment-16172398 ] Donald Szeto commented on PIO-68: - Cornell students implemented this: https://github.com/cbora/predictionio-template-java-universal-recommender > 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) Add link for guide for creating java templates to documentation
[ https://issues.apache.org/jira/browse/PIO-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-67: Labels: newbie (was: ) > 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 > Labels: newbie > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (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 ] Donald Szeto reassigned PIO-36: --- Assignee: Chan Target Version/s: 0.13.0-incubating > 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: Test >Reporter: Marcin Ziemiński >Assignee: Chan >Priority: Minor > > 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.4.14#64029)
[jira] [Updated] (PIO-7) document use of SSL
[ https://issues.apache.org/jira/browse/PIO-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-7: --- Labels: newbie (was: ) > document use of SSL > --- > > Key: PIO-7 > URL: https://issues.apache.org/jira/browse/PIO-7 > Project: PredictionIO > Issue Type: Sub-task > Components: Documentation >Reporter: Pat Ferrel >Assignee: Donald Szeto > Labels: newbie > > Document how to enable/disable SSL and manage certs, once pio-1 is ready -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-7) document use of SSL
[ https://issues.apache.org/jira/browse/PIO-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-7: --- Component/s: Documentation > document use of SSL > --- > > Key: PIO-7 > URL: https://issues.apache.org/jira/browse/PIO-7 > Project: PredictionIO > Issue Type: Sub-task > Components: Documentation >Reporter: Pat Ferrel >Assignee: Donald Szeto > Labels: newbie > > Document how to enable/disable SSL and manage certs, once pio-1 is ready -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PIO-7) document use of SSL
[ https://issues.apache.org/jira/browse/PIO-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto reassigned PIO-7: -- Assignee: (was: Donald Szeto) > document use of SSL > --- > > Key: PIO-7 > URL: https://issues.apache.org/jira/browse/PIO-7 > Project: PredictionIO > Issue Type: Sub-task > Components: Documentation >Reporter: Pat Ferrel > Labels: newbie > > Document how to enable/disable SSL and manage certs, once pio-1 is ready -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (PIO-122) always get Error initializing storage client for source ELASTICSEARCH in 0.11 when pio train
[
https://issues.apache.org/jira/browse/PIO-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170987#comment-16170987
]
Donald Szeto commented on PIO-122:
--
[~glorysdj], since you have closed this, did you find a solution?
> always get Error initializing storage client for source ELASTICSEARCH in 0.11
> when pio train
>
>
> Key: PIO-122
> URL: https://issues.apache.org/jira/browse/PIO-122
> Project: PredictionIO
> Issue Type: Bug
> Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: dongjie.shi
>
> Always get this error when I try to run PIO train to test a local PIO with
> HBase and Elasticsearch.
> [ERROR] [Storage$] Error initializing storage client for source ELASTICSEARCH
> Exception in thread "main"
> org.apache.predictionio.data.storage.StorageClientException: Data source
> ELASTICSEARCH was not properly initialized.
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at scala.Option.getOrElse(Option.scala:120)
> 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$.getMetaDataEngineInstances(Storage.scala:371)
> at
> org.apache.predictionio.workflow.CreateWorkflow$.main(CreateWorkflow.scala:247)
> 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:497)
> at
> org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:731)
> at org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:181)
> at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:206)
> at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:121)
> at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
> It seems that every component is ok in pio staus:
> [INFO] [Management$] Your system is all ready to go.
> And about the configurations in pio-env.conf, I have checked them for many
> times.
> PIO_FS_BASEDIR=${HOME}/.pio_store
> PIO_FS_ENGINESDIR=${PIO_FS_BASEDIR}/engines
> PIO_FS_TMPDIR=${PIO_FS_BASEDIR}/tmp
> SPARK_HOME=${SPARK_HOME}
> HBASE_CONF_DIR=${HBASE_HOME}/conf
> PIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_meta
> PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH
> PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event
> PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=HBASE
> PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model
> PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=LOCALFS
> PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch
> PIO_STORAGE_SOURCES_ELASTICSEARCH_CLUSTERNAME=predictionio
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS=localhost
> PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOME=${ELASTICSEARCH_HOME}
> PIO_STORAGE_SOURCES_LOCALFS_TYPE=localfs
> PIO_STORAGE_SOURCES_LOCALFS_PATH=${PIO_FS_BASEDIR}/models
> PIO_STORAGE_SOURCES_HBASE_TYPE=hbase
> PIO_STORAGE_SOURCES_HBASE_HOME=${HBASE_HOME}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PIO-122) always get Error initializing storage client for source ELASTICSEARCH in 0.11 when pio train
[
https://issues.apache.org/jira/browse/PIO-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167425#comment-16167425
]
Donald Szeto commented on PIO-122:
--
Can you provide information on
* how you built PIO 0.11
* the template you are using
* the {{conf/pio-env.sh}} of your PIO 0.11 build
* Elasticsearch version
* detail error message in {{pio.log}} where you run {{pio train}}
?
> always get Error initializing storage client for source ELASTICSEARCH in 0.11
> when pio train
>
>
> Key: PIO-122
> URL: https://issues.apache.org/jira/browse/PIO-122
> Project: PredictionIO
> Issue Type: Bug
> Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: dongjie.shi
>
> Always get this error when I try to run PIO train to test a local PIO with
> HBase and Elasticsearch.
> [ERROR] [Storage$] Error initializing storage client for source ELASTICSEARCH
> Exception in thread "main"
> org.apache.predictionio.data.storage.StorageClientException: Data source
> ELASTICSEARCH was not properly initialized.
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at
> org.apache.predictionio.data.storage.Storage$$anonfun$10.apply(Storage.scala:285)
> at scala.Option.getOrElse(Option.scala:120)
> 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$.getMetaDataEngineInstances(Storage.scala:371)
> at
> org.apache.predictionio.workflow.CreateWorkflow$.main(CreateWorkflow.scala:247)
> 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:497)
> at
> org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:731)
> at org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:181)
> at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:206)
> at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:121)
> at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
> It seems that every component is ok in pio staus:
> [INFO] [Management$] Your system is all ready to go.
> And about the configurations in pio-env.conf, I have checked them for many
> times.
> PIO_FS_BASEDIR=${HOME}/.pio_store
> PIO_FS_ENGINESDIR=${PIO_FS_BASEDIR}/engines
> PIO_FS_TMPDIR=${PIO_FS_BASEDIR}/tmp
> SPARK_HOME=${SPARK_HOME}
> HBASE_CONF_DIR=${HBASE_HOME}/conf
> PIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_meta
> PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH
> PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event
> PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=HBASE
> PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model
> PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=LOCALFS
> PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch
> PIO_STORAGE_SOURCES_ELASTICSEARCH_CLUSTERNAME=predictionio
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS=localhost
> PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300
> PIO_STORAGE_SOURCES_ELASTICSEARCH_HOME=${ELASTICSEARCH_HOME}
> PIO_STORAGE_SOURCES_LOCALFS_TYPE=localfs
> PIO_STORAGE_SOURCES_LOCALFS_PATH=${PIO_FS_BASEDIR}/models
> PIO_STORAGE_SOURCES_HBASE_TYPE=hbase
> PIO_STORAGE_SOURCES_HBASE_HOME=${HBASE_HOME}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (PIO-59) "pio app new" sometimes takes long time
[
https://issues.apache.org/jira/browse/PIO-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto updated PIO-59:
Component/s: Core
> "pio app new" sometimes takes long time
> ---
>
> Key: PIO-59
> URL: https://issues.apache.org/jira/browse/PIO-59
> Project: PredictionIO
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Shinsuke Sugaya
>Priority: Minor
> Fix For: 0.12.0-incubating
>
>
> Some users reported this problem in user ML, and I also encountered it.
> Checking stack traces, I think the cause is an entropy shortage for
> /dev/random.
> {code}
> "main" #1 prio=5 os_prio=0 tid=0x7fc94803f800 nid=0x49a9 runnable
> [0x7fc94fa1b000]
>java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at
> sun.security.provider.NativePRNG$RandomIO.readFully(NativePRNG.java:424)
> at
> sun.security.provider.NativePRNG$RandomIO.ensureBufferValid(NativePRNG.java:525)
> at
> sun.security.provider.NativePRNG$RandomIO.implNextBytes(NativePRNG.java:544)
> - locked <0x0003d34e8a48> (a java.lang.Object)
> at
> sun.security.provider.NativePRNG$RandomIO.access$400(NativePRNG.java:331)
> at
> sun.security.provider.NativePRNG$Blocking.engineNextBytes(NativePRNG.java:268)
> at java.security.SecureRandom.nextBytes(SecureRandom.java:468)
> at
> org.apache.predictionio.data.storage.AccessKeys$class.generateKey(AccessKeys.scala:71)
> at
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.generateKey(ESAccessKeys.scala:40)
> at
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.insert(ESAccessKeys.scala:60)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:71)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:62)
> at scala.Option.map(Option.scala:145)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:62)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:55)
> at scala.Option.getOrElse(Option.scala:120)
> at org.apache.predictionio.tools.commands.App$.create(App.scala:55)
> at
> org.apache.predictionio.tools.console.Pio$App$.create(Pio.scala:172)
> at
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:683)
> at
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:626)
> at scala.Option.map(Option.scala:145)
> at
> org.apache.predictionio.tools.console.Console$.main(Console.scala:626)
> at org.apache.predictionio.tools.console.Console.main(Console.scala)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (PIO-59) "pio app new" sometimes takes long time
[
https://issues.apache.org/jira/browse/PIO-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto updated PIO-59:
Fix Version/s: 0.12.0-incubating
> "pio app new" sometimes takes long time
> ---
>
> Key: PIO-59
> URL: https://issues.apache.org/jira/browse/PIO-59
> Project: PredictionIO
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Shinsuke Sugaya
>Priority: Minor
> Fix For: 0.12.0-incubating
>
>
> Some users reported this problem in user ML, and I also encountered it.
> Checking stack traces, I think the cause is an entropy shortage for
> /dev/random.
> {code}
> "main" #1 prio=5 os_prio=0 tid=0x7fc94803f800 nid=0x49a9 runnable
> [0x7fc94fa1b000]
>java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at
> sun.security.provider.NativePRNG$RandomIO.readFully(NativePRNG.java:424)
> at
> sun.security.provider.NativePRNG$RandomIO.ensureBufferValid(NativePRNG.java:525)
> at
> sun.security.provider.NativePRNG$RandomIO.implNextBytes(NativePRNG.java:544)
> - locked <0x0003d34e8a48> (a java.lang.Object)
> at
> sun.security.provider.NativePRNG$RandomIO.access$400(NativePRNG.java:331)
> at
> sun.security.provider.NativePRNG$Blocking.engineNextBytes(NativePRNG.java:268)
> at java.security.SecureRandom.nextBytes(SecureRandom.java:468)
> at
> org.apache.predictionio.data.storage.AccessKeys$class.generateKey(AccessKeys.scala:71)
> at
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.generateKey(ESAccessKeys.scala:40)
> at
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.insert(ESAccessKeys.scala:60)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:71)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:62)
> at scala.Option.map(Option.scala:145)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:62)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:55)
> at scala.Option.getOrElse(Option.scala:120)
> at org.apache.predictionio.tools.commands.App$.create(App.scala:55)
> at
> org.apache.predictionio.tools.console.Pio$App$.create(Pio.scala:172)
> at
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:683)
> at
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:626)
> at scala.Option.map(Option.scala:145)
> at
> org.apache.predictionio.tools.console.Console$.main(Console.scala:626)
> at org.apache.predictionio.tools.console.Console.main(Console.scala)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (PIO-59) "pio app new" sometimes takes long time
[
https://issues.apache.org/jira/browse/PIO-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto updated PIO-59:
Affects Version/s: 0.11.0-incubating
> "pio app new" sometimes takes long time
> ---
>
> Key: PIO-59
> URL: https://issues.apache.org/jira/browse/PIO-59
> Project: PredictionIO
> Issue Type: Improvement
>Affects Versions: 0.11.0-incubating
>Reporter: Shinsuke Sugaya
>Priority: Minor
>
> Some users reported this problem in user ML, and I also encountered it.
> Checking stack traces, I think the cause is an entropy shortage for
> /dev/random.
> {code}
> "main" #1 prio=5 os_prio=0 tid=0x7fc94803f800 nid=0x49a9 runnable
> [0x7fc94fa1b000]
>java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at
> sun.security.provider.NativePRNG$RandomIO.readFully(NativePRNG.java:424)
> at
> sun.security.provider.NativePRNG$RandomIO.ensureBufferValid(NativePRNG.java:525)
> at
> sun.security.provider.NativePRNG$RandomIO.implNextBytes(NativePRNG.java:544)
> - locked <0x0003d34e8a48> (a java.lang.Object)
> at
> sun.security.provider.NativePRNG$RandomIO.access$400(NativePRNG.java:331)
> at
> sun.security.provider.NativePRNG$Blocking.engineNextBytes(NativePRNG.java:268)
> at java.security.SecureRandom.nextBytes(SecureRandom.java:468)
> at
> org.apache.predictionio.data.storage.AccessKeys$class.generateKey(AccessKeys.scala:71)
> at
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.generateKey(ESAccessKeys.scala:40)
> at
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.insert(ESAccessKeys.scala:60)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:71)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:62)
> at scala.Option.map(Option.scala:145)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:62)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:55)
> at scala.Option.getOrElse(Option.scala:120)
> at org.apache.predictionio.tools.commands.App$.create(App.scala:55)
> at
> org.apache.predictionio.tools.console.Pio$App$.create(Pio.scala:172)
> at
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:683)
> at
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:626)
> at scala.Option.map(Option.scala:145)
> at
> org.apache.predictionio.tools.console.Console$.main(Console.scala:626)
> at org.apache.predictionio.tools.console.Console.main(Console.scala)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (PIO-99) `pio build` exits successfully even when compilation fails
[
https://issues.apache.org/jira/browse/PIO-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148202#comment-16148202
]
Donald Szeto edited comment on PIO-99 at 8/30/17 11:20 PM:
---
To reproduce:
# Build an engine that will return a successful run.
# Purposely introduce a syntax error in engine code.
# Build again.
This is a bug because log lines above mentioned it ran into an error and was
going to abort, but it did not and proceeded to check for build JARs, which
succeeded because there was a good previous build.
was (Author: dszeto):
To reproduce:
1. Build an engine that will return a successful run.
2. Purposely introduce a syntax error in engine code.
3. Build again.
This is a bug because log lines above mentioned it ran into an error and was
going to abort, but it did not and proceeded to check for build JARs, which
succeeded because there was a good previous build.
> `pio build` exits successfully even when compilation fails
> --
>
> Key: PIO-99
> URL: https://issues.apache.org/jira/browse/PIO-99
> Project: PredictionIO
> Issue Type: Bug
> Components: Build
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
> Labels: newbie
>
> The build command does not fail as expected. While not a big deal when
> working locally, it seems like this could be problematic for automated,
> continuous build/integration workflows.
> {code}
> $ pio build
> …
> [ERROR] [Engine$] [error] one error found
> [ERROR] [Engine$] [error] (compile:compileIncremental) Compilation failed
> [ERROR] [Engine$] [error] Total time: 5 s, completed Jun 21, 2017 9:59:55 AM
> [ERROR] [Engine$] Return code of build command:
> /Users/mars.hall/Projects/predictionio-engine-ur/PredictionIO-dist/sbt/sbt
> package assemblyPackageDependency is 1. Aborting.
> [INFO] [Engine$] Looking for an engine...
> [INFO] [Engine$] Found universal-recommender-assembly-0.5.0-deps.jar
> [INFO] [Engine$] Found universal-recommender_2.11-0.5.0.jar
> [INFO] [Engine$] Build finished successfully.
> [INFO] [Pio$] Your engine is ready for training.
> {code}
> It certainly appears successful at the end, and exit code was {{0}}.
> Looking back for the error is not hard, but this behavior is problematic when
> composing {{pio build}} command into a shell script.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PIO-99) `pio build` exits successfully even when compilation fails
[
https://issues.apache.org/jira/browse/PIO-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148202#comment-16148202
]
Donald Szeto commented on PIO-99:
-
To reproduce:
1. Build an engine that will return a successful run.
2. Purposely introduce a syntax error in engine code.
3. Build again.
This is a bug because log lines above mentioned it ran into an error and was
going to abort, but it did not and proceeded to check for build JARs, which
succeeded because there was a good previous build.
> `pio build` exits successfully even when compilation fails
> --
>
> Key: PIO-99
> URL: https://issues.apache.org/jira/browse/PIO-99
> Project: PredictionIO
> Issue Type: Bug
> Components: Build
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
> Labels: newbie
>
> The build command does not fail as expected. While not a big deal when
> working locally, it seems like this could be problematic for automated,
> continuous build/integration workflows.
> {code}
> $ pio build
> …
> [ERROR] [Engine$] [error] one error found
> [ERROR] [Engine$] [error] (compile:compileIncremental) Compilation failed
> [ERROR] [Engine$] [error] Total time: 5 s, completed Jun 21, 2017 9:59:55 AM
> [ERROR] [Engine$] Return code of build command:
> /Users/mars.hall/Projects/predictionio-engine-ur/PredictionIO-dist/sbt/sbt
> package assemblyPackageDependency is 1. Aborting.
> [INFO] [Engine$] Looking for an engine...
> [INFO] [Engine$] Found universal-recommender-assembly-0.5.0-deps.jar
> [INFO] [Engine$] Found universal-recommender_2.11-0.5.0.jar
> [INFO] [Engine$] Build finished successfully.
> [INFO] [Pio$] Your engine is ready for training.
> {code}
> It certainly appears successful at the end, and exit code was {{0}}.
> Looking back for the error is not hard, but this behavior is problematic when
> composing {{pio build}} command into a shell script.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (PIO-106) Elasticsearch 5.x StorageClient should reuse RestClient
[
https://issues.apache.org/jira/browse/PIO-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto updated PIO-106:
-
Target Version/s: 0.12.0-incubating
> Elasticsearch 5.x StorageClient should reuse RestClient
> ---
>
> Key: PIO-106
> URL: https://issues.apache.org/jira/browse/PIO-106
> Project: PredictionIO
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
>
> When using the proposed [PIO-105 Batch
> Predictions|https://issues.apache.org/jira/browse/PIO-105] feature with an
> engine that queries Elasticsearch in {{Algorithm#predict}}, Elasticsearch's
> REST interface appears to become overloaded, ending with the Spark job being
> killed from errors like:
> {noformat}
> [ERROR] [ESChannels] Failed to access to /pio_meta/channels/_search
> [ERROR] [Utils] Aborting task
> [ERROR] [ESApps] Failed to access to /pio_meta/apps/_search
> [ERROR] [Executor] Exception in task 747.0 in stage 1.0 (TID 749)
> [ERROR] [Executor] Exception in task 735.0 in stage 1.0 (TID 737)
> [ERROR] [Common$] Invalid app name ur
> [ERROR] [Utils] Aborting task
> [ERROR] [URAlgorithm] Error when read recent events:
> java.lang.IllegalArgumentException: Invalid app name ur
> [ERROR] [Executor] Exception in task 749.0 in stage 1.0 (TID 751)
> [ERROR] [Utils] Aborting task
> [ERROR] [Executor] Exception in task 748.0 in stage 1.0 (TID 750)
> [WARN] [TaskSetManager] Lost task 749.0 in stage 1.0 (TID 751, localhost,
> executor driver): java.net.BindException: Can't assign requested address
> at sun.nio.ch.Net.connect0(Native Method)
> at sun.nio.ch.Net.connect(Net.java:454)
> at sun.nio.ch.Net.connect(Net.java:446)
> at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
> at
> org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processSessionRequests(DefaultConnectingIOReactor.java:273)
> at
> org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:139)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348)
> at
> org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:192)
> at
> org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> After these errors happen & the job is killed, Elasticsearch immediately
> recovers. It responds to queries normally. I researched what could cause this
> and found an [old issue in the main Elasticsearch
> repo|https://github.com/elastic/elasticsearch/issues/3647]. With the hints
> given therein about *using keep-alive in the ES client* to avoid these
> performance issues, I investigated how PredictionIO's [Elasticsearch
> StorageClient|https://github.com/apache/incubator-predictionio/tree/develop/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch]
> manages its connections.
> I found that unlike the other StorageClients (Elasticsearch1, HBase, JDBC),
> Elasticsearch creates a new underlying connection, an Elasticsearch
> RestClient, for
> [every|https://github.com/apache/incubator-predictionio/blob/develop/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESApps.scala#L80]
>
> [single|https://github.com/apache/incubator-predictionio/blob/develop/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESApps.scala#L157]
>
> [query|https://github.com/apache/incubator-predictionio/blob/develop/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESChannels.scala#L78]
> &
> [interaction|https://github.com/apache/incubator-predictionio/blob/develop/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESEngineInstances.scala#L205]
> with its API. As a result, *there is no way Elasticsearch TCP connections
> can be reused via HTTP keep-alive*.
> High-performance workloads with Elasticsearch 5.x will suffer from these
> issues unless we refactor Elasticsearch StorageClient to share the underlying
> RestClient instead of [building a new one everytime the client is
> used|https://github.com/apache/incubator-predictionio/blob/develop/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/StorageClient.scala#L31].
> There are certainly different approaches we could take to sharing a
> RestClient so that its keep-alive behavior may work as designed:
> * maintain a singleton RestClient that is reused throughout the ES storage
> classes
> * create a RestClient on-demand and pass it
[jira] [Updated] (PIO-99) `pio build` exits successfully even when compilation fails
[
https://issues.apache.org/jira/browse/PIO-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto updated PIO-99:
Target Version/s: 0.12.0-incubating
> `pio build` exits successfully even when compilation fails
> --
>
> Key: PIO-99
> URL: https://issues.apache.org/jira/browse/PIO-99
> Project: PredictionIO
> Issue Type: Bug
> Components: Build
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
> Labels: newbie
>
> The build command does not fail as expected. While not a big deal when
> working locally, it seems like this could be problematic for automated,
> continuous build/integration workflows.
> {code}
> $ pio build
> …
> [ERROR] [Engine$] [error] one error found
> [ERROR] [Engine$] [error] (compile:compileIncremental) Compilation failed
> [ERROR] [Engine$] [error] Total time: 5 s, completed Jun 21, 2017 9:59:55 AM
> [ERROR] [Engine$] Return code of build command:
> /Users/mars.hall/Projects/predictionio-engine-ur/PredictionIO-dist/sbt/sbt
> package assemblyPackageDependency is 1. Aborting.
> [INFO] [Engine$] Looking for an engine...
> [INFO] [Engine$] Found universal-recommender-assembly-0.5.0-deps.jar
> [INFO] [Engine$] Found universal-recommender_2.11-0.5.0.jar
> [INFO] [Engine$] Build finished successfully.
> [INFO] [Pio$] Your engine is ready for training.
> {code}
> It certainly appears successful at the end, and exit code was {{0}}.
> Looking back for the error is not hard, but this behavior is problematic when
> composing {{pio build}} command into a shell script.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (PIO-105) Batch Predictions
[
https://issues.apache.org/jira/browse/PIO-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto updated PIO-105:
-
Target Version/s: 0.12.0-incubating
> Batch Predictions
> -
>
> Key: PIO-105
> URL: https://issues.apache.org/jira/browse/PIO-105
> Project: PredictionIO
> Issue Type: New Feature
> Components: Core
>Reporter: Mars Hall
>Assignee: Mars Hall
> Fix For: 0.12.0-incubating
>
>
> Implement a new {{pio batchpredict}} command to enable massive, fast, batch
> predictions from a trained model. Read a multi-object JSON file as the input
> format, with one query object per line. Similarly, write results to a
> multi-object JSON file, with one prediction result + its original query per
> line.
> Currently getting bulk predictions from PredictionIO is possible with either:
> * a {{pio eval}} script, which will always train a fresh, unvalidated model
> before getting predictions
> * a custom script that hits the {{queries.json}} HTTP API, which is a serious
> bottleneck when requesting hundreds-of-thousands or millions of predictions
> Neither of these existing bulk-prediction hacks are adequate for the reasons
> mentioned.
> It's time for this use-case to be a firstclass command :D
> Pull request https://github.com/apache/incubator-predictionio/pull/412
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (PIO-102) ESEngineInstances `getAll` results out of order (Elasticsearch 5.x)
[ https://issues.apache.org/jira/browse/PIO-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-102: - Target Version/s: 0.12.0-incubating > ESEngineInstances `getAll` results out of order (Elasticsearch 5.x) > --- > > Key: PIO-102 > URL: https://issues.apache.org/jira/browse/PIO-102 > Project: PredictionIO > Issue Type: Bug > Components: Core >Affects Versions: 0.11.0-incubating >Reporter: Mars Hall >Assignee: Mars Hall > Fix For: 0.12.0-incubating > > > Using the new Elasticsearch 5.x REST storage client as the meta storage > source (`PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH` setup in > conf/pio-env.sh), I found that once an engine has been trained a certain > number of times, that the most recent engine instance is no longer retrieved. > So, I tracked down where those Elasticsearch queries originate. > In the original Elasticsearch 1.x storage client, [the "scroll" pagination > responses are collected by > *appending*|https://github.com/apache/incubator-predictionio/blob/release/0.11.0/storage/elasticsearch1/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESUtils.scala#L44] > them to one another. > In the new Elasticsearch 5.x client, [the "scroll" responses are collected by > *prepending*|https://github.com/apache/incubator-predictionio/blob/release/0.11.0/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESUtils.scala#L152] > them to one another. > This out-of-order concatenation breaks [ESEngineInstances > `getLatestCompleted`|https://github.com/apache/incubator-predictionio/blob/release/0.11.0/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESEngineInstances.scala#L192] > by erroneously replacing the head of the results with an older engine > instance, when there are enough engine instances to overflow a single page of > Elasticsearch hits. > I've observed this buggy behavior after ten trainings, when enough engine > instances are stored to trigger Elasticsearch's scroll feature. > Pull request: https://github.com/apache/incubator-predictionio/pull/406 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-100) Remove SLF4J warning messages on pio command
[
https://issues.apache.org/jira/browse/PIO-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto updated PIO-100:
-
Target Version/s: 0.12.0-incubating
> Remove SLF4J warning messages on pio command
> -
>
> Key: PIO-100
> URL: https://issues.apache.org/jira/browse/PIO-100
> Project: PredictionIO
> Issue Type: Improvement
>Reporter: Shinsuke Sugaya
>Assignee: Shinsuke Sugaya
>Priority: Minor
>
> pio command prints SLF4J warning as below:
> {code}
> $ /usr/share/predictionio/bin/pio status
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/usr/share/predictionio/lib/spark/pio-data-hdfs-assembly-0.11.1-v1-SNAPSHOT.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/usr/share/predictionio/lib/pio-assembly-0.11.1-v1-SNAPSHOT.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]
> ...
> {code}
> The cause is that pio-data-hdfs contains slf4j-log4j12 jar file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (PIO-115) Cache name-to-ID lookups for Storage app & channel
[ https://issues.apache.org/jira/browse/PIO-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-115: - Target Version/s: 0.12.0-incubating > Cache name-to-ID lookups for Storage app & channel > -- > > Key: PIO-115 > URL: https://issues.apache.org/jira/browse/PIO-115 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Affects Versions: 0.11.0-incubating >Reporter: Mars Hall >Assignee: Mars Hall > > When stress testing the Universal Recommender with high-concurrency HTTP/REST > queries, we observed that Elasticsearch traffic was majority composed of > requests resolving the Storage app's name & channel, over and over and over > again! In this case, [each per-query call to > `LEventStore.findByEntity`|https://github.com/heroku/predictionio-engine-ur/blob/master/src/main/scala/URAlgorithm.scala#L694] > re-resolves the app name to an ID. > Implement memoization for the function that performs these name-to-ID > lookups, so that only one set of lookups is performed per process for each > app+channel combination. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (PIO-111) Document pio batchpredict
[
https://issues.apache.org/jira/browse/PIO-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto updated PIO-111:
-
Target Version/s: 0.12.0-incubating
> Document pio batchpredict
> -
>
> Key: PIO-111
> URL: https://issues.apache.org/jira/browse/PIO-111
> Project: PredictionIO
> Issue Type: Task
> Components: Documentation
>Affects Versions: 0.12.0-incubating
>Reporter: Donald Szeto
>Assignee: Mars Hall
> Labels: newbie
> Fix For: 0.12.0-incubating
>
>
> {{pio batchpredict}} is a new feature created in PIO-105. It needs to be
> documented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (PIO-114) Elasticsearch 5.x StorageClient basic HTTP authentication
[
https://issues.apache.org/jira/browse/PIO-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto updated PIO-114:
-
Target Version/s: 0.12.0-incubating
> Elasticsearch 5.x StorageClient basic HTTP authentication
> -
>
> Key: PIO-114
> URL: https://issues.apache.org/jira/browse/PIO-114
> Project: PredictionIO
> Issue Type: New Feature
> Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
>
> Add optional username-password configuration for the new Elasticsearch 5
> client; in {{conf/pio-env.sh}} config:
> {code}
> # Optional basic HTTP auth
> PIO_STORAGE_SOURCES_ELASTICSEARCH_USERNAME=my-name
> PIO_STORAGE_SOURCES_ELASTICSEARCH_PASSWORD=my-secret
> {code}
> These credentials are sent in each Elasticsearch request as an HTTP Basic
> Authorization header.
> Enables use of public-cloud, hosted Elasticsearch clusters, such as [Bonsai
> on Heroku](https://elements.heroku.com/addons/bonsai).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (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 ] Donald Szeto resolved PIO-66. - Resolution: Fixed Assignee: Takako Shimamoto (was: Sara Asher) Fix Version/s: 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: Takako Shimamoto > Fix For: 0.12.0-incubating > > > https://docs.google.com/document/d/1nQpENncXZq72KeI3WMe_X8Xz8HKkYO2QC12GD3ZKP9g/edit#heading=h.4og7ud94e5g1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (PIO-111) Document pio batchpredict
[
https://issues.apache.org/jira/browse/PIO-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto resolved PIO-111.
--
Resolution: Fixed
Fix Version/s: 0.12.0-incubating
> Document pio batchpredict
> -
>
> Key: PIO-111
> URL: https://issues.apache.org/jira/browse/PIO-111
> Project: PredictionIO
> Issue Type: Task
> Components: Documentation
>Affects Versions: 0.12.0-incubating
>Reporter: Donald Szeto
>Assignee: Mars Hall
> Labels: newbie
> Fix For: 0.12.0-incubating
>
>
> {{pio batchpredict}} is a new feature created in PIO-105. It needs to be
> documented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (PIO-63) Fix incubator branding issues
[
https://issues.apache.org/jira/browse/PIO-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto resolved PIO-63.
-
Resolution: Fixed
Assignee: Naoki Takezoe (was: Donald Szeto)
Fix 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
>Assignee: Naoki Takezoe
> Fix For: 0.12.0-incubating
>
>
> {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.4.14#64029)
[jira] [Resolved] (PIO-105) Batch Predictions
[
https://issues.apache.org/jira/browse/PIO-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto resolved PIO-105.
--
Resolution: Fixed
Fix Version/s: 0.12.0-incubating
> Batch Predictions
> -
>
> Key: PIO-105
> URL: https://issues.apache.org/jira/browse/PIO-105
> Project: PredictionIO
> Issue Type: New Feature
> Components: Core
>Reporter: Mars Hall
>Assignee: Mars Hall
> Fix For: 0.12.0-incubating
>
>
> Implement a new {{pio batchpredict}} command to enable massive, fast, batch
> predictions from a trained model. Read a multi-object JSON file as the input
> format, with one query object per line. Similarly, write results to a
> multi-object JSON file, with one prediction result + its original query per
> line.
> Currently getting bulk predictions from PredictionIO is possible with either:
> * a {{pio eval}} script, which will always train a fresh, unvalidated model
> before getting predictions
> * a custom script that hits the {{queries.json}} HTTP API, which is a serious
> bottleneck when requesting hundreds-of-thousands or millions of predictions
> Neither of these existing bulk-prediction hacks are adequate for the reasons
> mentioned.
> It's time for this use-case to be a firstclass command :D
> Pull request https://github.com/apache/incubator-predictionio/pull/412
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (PIO-111) Document pio batchpredict
Donald Szeto created PIO-111:
Summary: Document pio batchpredict
Key: PIO-111
URL: https://issues.apache.org/jira/browse/PIO-111
Project: PredictionIO
Issue Type: Task
Components: Documentation
Affects Versions: 0.12.0-incubating
Reporter: Donald Szeto
{{pio batchpredict}} is a new feature created in PIO-105. It needs to be
documented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (PIO-110) Refactor common code shared by CreateServer and BatchPredict
Donald Szeto created PIO-110:
Summary: Refactor common code shared by CreateServer and
BatchPredict
Key: PIO-110
URL: https://issues.apache.org/jira/browse/PIO-110
Project: PredictionIO
Issue Type: Improvement
Components: Core
Affects Versions: 0.12.0-incubating
Reporter: Donald Szeto
{{BatchPredict}} was created in PIO-105 and has a substantial amount of shared
code with {{CreateServer}}. It would be beneficial to refactor both of them to
share as much common code as possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (PIO-110) Refactor common code shared by CreateServer and BatchPredict
[
https://issues.apache.org/jira/browse/PIO-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109721#comment-16109721
]
Donald Szeto commented on PIO-110:
--
Please follow [~takezoe]'s code style advice on
https://github.com/apache/incubator-predictionio/pull/412.
> Refactor common code shared by CreateServer and BatchPredict
>
>
> Key: PIO-110
> URL: https://issues.apache.org/jira/browse/PIO-110
> Project: PredictionIO
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.12.0-incubating
>Reporter: Donald Szeto
> Labels: newbie
>
> {{BatchPredict}} was created in PIO-105 and has a substantial amount of
> shared code with {{CreateServer}}. It would be beneficial to refactor both of
> them to share as much common code as possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (PIO-104) Make proper implementation of plugins
[ https://issues.apache.org/jira/browse/PIO-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-104. -- Resolution: Fixed Fix Version/s: 0.12.0-incubating > Make proper implementation of plugins > - > > Key: PIO-104 > URL: https://issues.apache.org/jira/browse/PIO-104 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Affects Versions: 0.11.0-incubating >Reporter: Naoki Takezoe >Assignee: Naoki Takezoe > Fix For: 0.12.0-incubating > > > The current plugin system has some issues to be fixed: > - start() method of plugin is not called, this method seems to be unnecessary > - outputSniffer exists as interface, but it's not implemented in engine server > We should fix them before documenting plugin usage in PIO-101 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (PIO-102) ESEngineInstances `getAll` results out of order (Elasticsearch 5.x)
[ https://issues.apache.org/jira/browse/PIO-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-102. -- Resolution: Fixed Fix Version/s: 0.12.0-incubating > ESEngineInstances `getAll` results out of order (Elasticsearch 5.x) > --- > > Key: PIO-102 > URL: https://issues.apache.org/jira/browse/PIO-102 > Project: PredictionIO > Issue Type: Bug > Components: Core >Affects Versions: 0.11.0-incubating >Reporter: Mars Hall >Assignee: Mars Hall > Fix For: 0.12.0-incubating > > > Using the new Elasticsearch 5.x REST storage client as the meta storage > source (`PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH` setup in > conf/pio-env.sh), I found that once an engine has been trained a certain > number of times, that the most recent engine instance is no longer retrieved. > So, I tracked down where those Elasticsearch queries originate. > In the original Elasticsearch 1.x storage client, [the "scroll" pagination > responses are collected by > *appending*|https://github.com/apache/incubator-predictionio/blob/release/0.11.0/storage/elasticsearch1/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESUtils.scala#L44] > them to one another. > In the new Elasticsearch 5.x client, [the "scroll" responses are collected by > *prepending*|https://github.com/apache/incubator-predictionio/blob/release/0.11.0/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESUtils.scala#L152] > them to one another. > This out-of-order concatenation breaks [ESEngineInstances > `getLatestCompleted`|https://github.com/apache/incubator-predictionio/blob/release/0.11.0/storage/elasticsearch/src/main/scala/org/apache/predictionio/data/storage/elasticsearch/ESEngineInstances.scala#L192] > by erroneously replacing the head of the results with an older engine > instance, when there are enough engine instances to overflow a single page of > Elasticsearch hits. > I've observed this buggy behavior after ten trainings, when enough engine > instances are stored to trigger Elasticsearch's scroll feature. > Pull request: https://github.com/apache/incubator-predictionio/pull/406 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (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
]
Donald Szeto resolved PIO-72.
-
Resolution: Fixed
Fix Version/s: 0.12.0-incubating
> 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
> Fix For: 0.12.0-incubating
>
> 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
[jira] [Assigned] (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 ] Donald Szeto reassigned PIO-56: --- Assignee: Lucas Bonatto Miguel > 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 >Assignee: Lucas Bonatto Miguel > Labels: development_environment > Fix For: 0.12.0-incubating > > > *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.4.14#64029)
[jira] [Updated] (PIO-99) `pio build` exits successfully even when compilation fails
[
https://issues.apache.org/jira/browse/PIO-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto updated PIO-99:
Labels: newbie (was: )
> `pio build` exits successfully even when compilation fails
> --
>
> Key: PIO-99
> URL: https://issues.apache.org/jira/browse/PIO-99
> Project: PredictionIO
> Issue Type: Bug
> Components: Build
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
> Labels: newbie
>
> The build command does not fail as expected. While not a big deal when
> working locally, it seems like this could be problematic for automated,
> continuous build/integration workflows.
> {code}
> $ pio build
> …
> [ERROR] [Engine$] [error] one error found
> [ERROR] [Engine$] [error] (compile:compileIncremental) Compilation failed
> [ERROR] [Engine$] [error] Total time: 5 s, completed Jun 21, 2017 9:59:55 AM
> [ERROR] [Engine$] Return code of build command:
> /Users/mars.hall/Projects/predictionio-engine-ur/PredictionIO-dist/sbt/sbt
> package assemblyPackageDependency is 1. Aborting.
> [INFO] [Engine$] Looking for an engine...
> [INFO] [Engine$] Found universal-recommender-assembly-0.5.0-deps.jar
> [INFO] [Engine$] Found universal-recommender_2.11-0.5.0.jar
> [INFO] [Engine$] Build finished successfully.
> [INFO] [Pio$] Your engine is ready for training.
> {code}
> It certainly appears successful at the end, and exit code was {{0}}.
> Looking back for the error is not hard, but this behavior is problematic when
> composing {{pio build}} command into a shell script.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (PIO-95) Configurable request timeout for REST API
[ https://issues.apache.org/jira/browse/PIO-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-95. - Resolution: Fixed Fix Version/s: 0.12.0-incubating Target Version/s: 0.12.0-incubating > Configurable request timeout for REST API > - > > Key: PIO-95 > URL: https://issues.apache.org/jira/browse/PIO-95 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Affects Versions: 0.11.0-incubating >Reporter: Mars Hall >Assignee: Mars Hall > Fix For: 0.12.0-incubating > > > We've found the default 20-second REST API request timeout is too short for > our batch-prediction use cases. We're running PredictionIO on Heroku which > has its own [timeout starting at > 30-seconds|https://devcenter.heroku.com/articles/limits#http-timeouts]. So > we'd prefer a more generous or easily configurable timeout to allow Heroku's > routing layer to impose & track this limit in the platform layer. > I investigated how to configure this and found [Spray > `application.conf`|http://spray.io/documentation/1.2.4/spray-can/configuration/]. > This PR simply increases the timeout. > I would love guidance on how we might extract this config into an environment > variable or a value in `pio-env.sh`. > Investigation / implementation PR: > https://github.com/apache/incubator-predictionio/pull/394 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (PIO-95) Configurable request timeout for REST API
[ https://issues.apache.org/jira/browse/PIO-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto reassigned PIO-95: --- Assignee: Mars Hall > Configurable request timeout for REST API > - > > Key: PIO-95 > URL: https://issues.apache.org/jira/browse/PIO-95 > Project: PredictionIO > Issue Type: Improvement > Components: Core >Affects Versions: 0.11.0-incubating >Reporter: Mars Hall >Assignee: Mars Hall > Fix For: 0.12.0-incubating > > > We've found the default 20-second REST API request timeout is too short for > our batch-prediction use cases. We're running PredictionIO on Heroku which > has its own [timeout starting at > 30-seconds|https://devcenter.heroku.com/articles/limits#http-timeouts]. So > we'd prefer a more generous or easily configurable timeout to allow Heroku's > routing layer to impose & track this limit in the platform layer. > I investigated how to configure this and found [Spray > `application.conf`|http://spray.io/documentation/1.2.4/spray-can/configuration/]. > This PR simply increases the timeout. > I would love guidance on how we might extract this config into an environment > variable or a value in `pio-env.sh`. > Investigation / implementation PR: > https://github.com/apache/incubator-predictionio/pull/394 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (PIO-94) Query parsing may throw intractable errors
[
https://issues.apache.org/jira/browse/PIO-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto resolved PIO-94.
-
Resolution: Fixed
Fix Version/s: 0.12.0-incubating
Target Version/s: 0.12.0-incubating
> Query parsing may throw intractable errors
> --
>
> Key: PIO-94
> URL: https://issues.apache.org/jira/browse/PIO-94
> Project: PredictionIO
> Issue Type: Bug
> Components: Core
>Affects Versions: 0.11.0-incubating
>Reporter: Mars Hall
>Assignee: Mars Hall
> Fix For: 0.12.0-incubating
>
>
> We get intractable errors from some `queries.json` requests, like this one
> without a stacktrace:
> {code}
> [ERROR] [ServerActor] Query '{
> "item": "000"
> }' is invalid. Reason: Expected object but got JNothing
> {code}
> To solve, add stacktraces to these errors using the pattern already present
> elsewhere in `CreateServer.scala`.
> PR: https://github.com/apache/incubator-predictionio/pull/393
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (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 ] Donald Szeto resolved PIO-65. - Resolution: Fixed Fix 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 > Fix For: 0.12.0-incubating > > > 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] [Commented] (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:comment-tabpanel=16037643#comment-16037643 ] Donald Szeto commented on PIO-69: - Hey [~shinsuke], the main issue here is that Apache requires auditing all bundled 3rd party libraries in any binary distributions that would be uploaded to the Apache distribution network. Our make-distribution.sh script already handles creating the binary distribution part. What is missing here is to make sure the binary distribution only contains 3rd party libraries that are compatible with the APLv2 license. > 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 >Assignee: Shinsuke Sugaya > -- 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 ] Donald Szeto updated PIO-61: Fix Version/s: 0.12.0-incubating > 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 > Fix For: 0.12.0-incubating > > > 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] [Resolved] (PIO-61) Add S3 Model Data Repository
[ https://issues.apache.org/jira/browse/PIO-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-61. - Resolution: Fixed > 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 > Fix For: 0.12.0-incubating > > > 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] [Assigned] (PIO-71) Support Spark ML natively as an alternative to DASE
[ https://issues.apache.org/jira/browse/PIO-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto reassigned PIO-71: --- Assignee: Donald Szeto > Support Spark ML natively as an alternative to DASE > --- > > Key: PIO-71 > URL: https://issues.apache.org/jira/browse/PIO-71 > Project: PredictionIO > Issue Type: New Feature > Components: Core >Affects Versions: 0.11.0-incubating >Reporter: Donald Szeto >Assignee: Donald Szeto > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-71) Support Spark ML natively as an alternative to DASE
Donald Szeto created PIO-71: --- Summary: Support Spark ML natively as an alternative to DASE Key: PIO-71 URL: https://issues.apache.org/jira/browse/PIO-71 Project: PredictionIO Issue Type: New Feature Components: Core Affects Versions: 0.11.0-incubating Reporter: Donald Szeto -- 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
]
Donald Szeto updated PIO-64:
Fix Version/s: (was: 0.11.1-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
> 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
> -> JDouble(4.56), prop1 ->
[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
]
Donald Szeto updated PIO-62:
Labels: newbie (was: )
> 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] [Created] (PIO-64) JDBCPEvents unit tests fail intermittently
Donald Szeto created PIO-64:
---
Summary: 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
Fix For: 0.11.1-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:
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)
(PEventsSpec.scala:190)
[info]
[info]
[info]
[info] - (table
[jira] [Created] (PIO-63) Fix incubator branding issues
Donald Szeto created PIO-63:
---
Summary: 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] [Created] (PIO-62) Investigate RAT issues and other authorship information
Donald Szeto created PIO-62:
---
Summary: 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
{quote}
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
{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] [Created] (PIO-60) Fix minor issues with author information
Donald Szeto created PIO-60: --- Summary: 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] [Commented] (PIO-59) "pio app new" sometimes takes long time
[
https://issues.apache.org/jira/browse/PIO-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955428#comment-15955428
]
Donald Szeto commented on PIO-59:
-
Are you running on VM or container? Our integration tests use
http://www.issihosts.com/haveged/ to resolve this issue.
> "pio app new" sometimes takes long time
> ---
>
> Key: PIO-59
> URL: https://issues.apache.org/jira/browse/PIO-59
> Project: PredictionIO
> Issue Type: Improvement
>Reporter: Shinsuke Sugaya
>Priority: Minor
>
> Some users reported this problem in user ML, and I also encountered it.
> Checking stack traces, I think the cause is an entropy shortage for
> /dev/random.
> {code}
> "main" #1 prio=5 os_prio=0 tid=0x7fc94803f800 nid=0x49a9 runnable
> [0x7fc94fa1b000]
>java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at
> sun.security.provider.NativePRNG$RandomIO.readFully(NativePRNG.java:424)
> at
> sun.security.provider.NativePRNG$RandomIO.ensureBufferValid(NativePRNG.java:525)
> at
> sun.security.provider.NativePRNG$RandomIO.implNextBytes(NativePRNG.java:544)
> - locked <0x0003d34e8a48> (a java.lang.Object)
> at
> sun.security.provider.NativePRNG$RandomIO.access$400(NativePRNG.java:331)
> at
> sun.security.provider.NativePRNG$Blocking.engineNextBytes(NativePRNG.java:268)
> at java.security.SecureRandom.nextBytes(SecureRandom.java:468)
> at
> org.apache.predictionio.data.storage.AccessKeys$class.generateKey(AccessKeys.scala:71)
> at
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.generateKey(ESAccessKeys.scala:40)
> at
> org.apache.predictionio.data.storage.elasticsearch.ESAccessKeys.insert(ESAccessKeys.scala:60)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:71)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4$$anonfun$apply$5.apply(App.scala:62)
> at scala.Option.map(Option.scala:145)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:62)
> at
> org.apache.predictionio.tools.commands.App$$anonfun$create$4.apply(App.scala:55)
> at scala.Option.getOrElse(Option.scala:120)
> at org.apache.predictionio.tools.commands.App$.create(App.scala:55)
> at
> org.apache.predictionio.tools.console.Pio$App$.create(Pio.scala:172)
> at
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:683)
> at
> org.apache.predictionio.tools.console.Console$$anonfun$main$1.apply(Console.scala:626)
> at scala.Option.map(Option.scala:145)
> at
> org.apache.predictionio.tools.console.Console$.main(Console.scala:626)
> at org.apache.predictionio.tools.console.Console.main(Console.scala)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (PIO-32) create component upgrade releases
[ https://issues.apache.org/jira/browse/PIO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-32: Labels: gsoc2017 (was: ) > create component upgrade releases > - > > Key: PIO-32 > URL: https://issues.apache.org/jira/browse/PIO-32 > Project: PredictionIO > Issue Type: New Feature >Affects Versions: future release >Reporter: Pat Ferrel > Labels: gsoc2017 > Fix For: future release > > > 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.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 ] Donald Szeto updated PIO-31: Labels: gsoc2017 (was: ) > 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 >Reporter: Marcin Ziemiński > Labels: gsoc2017 > > 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] [Resolved] (PIO-57) Add SBT Native Packager
[ https://issues.apache.org/jira/browse/PIO-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-57. - Resolution: Fixed Fix Version/s: 0.11.0 > Add SBT Native Packager > --- > > Key: PIO-57 > URL: https://issues.apache.org/jira/browse/PIO-57 > Project: PredictionIO > Issue Type: New Feature >Reporter: Shinsuke Sugaya > Fix For: 0.11.0 > > > To use SBT Native Packager, we will provide RPM/DEB distribution packages in > addition to ZIP/TAR.GZ. > This fix is: > * make-distribution.sh is still available > ** Created: PredictionIO-*.tar.gz > * Create TAR.GZ/ZIP package > ** Run ./make-distribution.sh > ** Created: assembly/target/universal/predictionio-* > * Create RPM package: > ** Run ./make-distribution.sh;./sbt/sbt assembly/rpm:packageBin > ** Created: assembly/target/rpm/RPMS/noarch/predictionio-*.rpm > * Create DEB package > ** Run ./make-distribution.sh;./sbt/sbt assembly/debian:packageBin > ** Created: assembly/target/predictionio_*.deb > For RPM/DEB package: > * PIO_HOME is /usr/share/predictionio. > * pio command is in /usr/bin. > * conf files are in /etc/predictionio. > * log files is /var/log/predictionio/pio.log if you have write permission, or > $HOME/pio.log if not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Deleted] (PIO-58) ifgfikvjuk
[ https://issues.apache.org/jira/browse/PIO-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto deleted PIO-58: > ifgfikvjuk > -- > > Key: PIO-58 > URL: https://issues.apache.org/jira/browse/PIO-58 > Project: PredictionIO > Issue Type: Bug >Reporter: Donald Szeto > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-58) ifgfikvjuk
Donald Szeto created PIO-58: --- Summary: ifgfikvjuk Key: PIO-58 URL: https://issues.apache.org/jira/browse/PIO-58 Project: PredictionIO Issue Type: Bug Reporter: Donald Szeto -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (PIO-49) Add support for Elasticsearch 5.x
[ https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-49. - Resolution: Fixed > Add support for Elasticsearch 5.x > - > > Key: PIO-49 > URL: https://issues.apache.org/jira/browse/PIO-49 > Project: PredictionIO > Issue Type: Improvement >Reporter: Shinsuke Sugaya >Assignee: Donald Szeto >Priority: Blocker > Fix For: 0.11.0 > > > We work on meta/event storage support for Elasticsearch 5.x. > Although Elasticsearch 2.x does not allow dots in field names, > Elasticsearch 5.x supports it. So, it's better to upgrade to ES 5.x release. > Since ES 5.x provides Java Rest API client, we replaced > Transport communication with HTTP one. Therefore, our fix > uses HTTP(9200 port) only. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (PIO-30) Cross build for different versions of scala and spark
[ https://issues.apache.org/jira/browse/PIO-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-30. - Resolution: Fixed > Cross build for different versions of scala and spark > - > > Key: PIO-30 > URL: https://issues.apache.org/jira/browse/PIO-30 > Project: PredictionIO > Issue Type: Improvement >Reporter: Marcin Ziemiński >Assignee: Chan > Fix For: 0.11.0 > > > The present version of Scala is 2.10 and Spark is 1.4, which is quite old. > With Spark 2.0.0 come many performance improvements and features, that people > will definitely like to add to their templates. I am also aware that past > cannot be ignored and simply dumping 1.x might not be an option for other > users. > I propose setting up a crossbuild in sbt to build with scala 2.10 and Spark > 1.6 and a separate one for Scala 2.11 and Spark 2.0. Most of the files will > be consistent between versions including API. The problematic ones will be > divided between additional source directories: src/main/scala-2.10/ and > src/main/scala-2.11/. The dockerized tests should also take the two versions > into consideration -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (PIO-25) Don't attempt to start PostgreSQL when it's not being used
[
https://issues.apache.org/jira/browse/PIO-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto resolved PIO-25.
-
Resolution: Fixed
Fix Version/s: 0.11.0
> Don't attempt to start PostgreSQL when it's not being used
> --
>
> Key: PIO-25
> URL: https://issues.apache.org/jira/browse/PIO-25
> Project: PredictionIO
> Issue Type: Improvement
>Reporter: David Jones
>Priority: Trivial
> Fix For: 0.11.0
>
>
> When running: {{pio-start-all}}, even if your {{pio-env.sh}} file is setup to
> use HBase and not PostgreSQL you'll see "postgresql: unrecognised service":
> {quote}
> Starting Elasticsearch...
> Starting HBase...
> starting master, logging to
> /PredictionIO/vendors/hbase-1.2.2/bin/../logs/hbase--master-2898ebbfb9d1.out
> postgresql: unrecognized service
> Waiting 10 seconds for HBase to fully initialize...
> Starting PredictionIO Event Server...
> {quote}
> This is because {{pio-start-all}} simply tries to detect if PostgreSQL is
> running, if it isn't, then it will go ahead and try to start it:
> https://github.com/apache/incubator-predictionio/blob/develop/bin/pio-start-all#L64
> What would be better is if we checked
> {{PIO_STORAGE_REPOSITORIES_METADATA_SOURCE}},
> {{PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE}} and
> {{PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE}} to see if any of those have
> been set to {{PGSQL}}. If they have not been set to {{PGSQL}} then we don't
> need to attempt to start PostgreSQL every time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (PIO-49) Add support for Elasticsearch 5.x
[ https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-49. - Resolution: Fixed Fix Version/s: 0.11.0 > Add support for Elasticsearch 5.x > - > > Key: PIO-49 > URL: https://issues.apache.org/jira/browse/PIO-49 > Project: PredictionIO > Issue Type: Improvement >Reporter: Shinsuke Sugaya > Fix For: 0.11.0 > > > We work on meta/event storage support for Elasticsearch 5.x. > Although Elasticsearch 2.x does not allow dots in field names, > Elasticsearch 5.x supports it. So, it's better to upgrade to ES 5.x release. > Since ES 5.x provides Java Rest API client, we replaced > Transport communication with HTTP one. Therefore, our fix > uses HTTP(9200 port) only. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (PIO-53) Create per-commit Docker image for testing
[ https://issues.apache.org/jira/browse/PIO-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-53. - Resolution: Fixed > Create per-commit Docker image for testing > -- > > Key: PIO-53 > URL: https://issues.apache.org/jira/browse/PIO-53 > Project: PredictionIO > Issue Type: Test >Reporter: Donald Szeto >Assignee: Donald Szeto > Fix For: 0.11.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-54) Avoid access key started with -
[
https://issues.apache.org/jira/browse/PIO-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto updated PIO-54:
Fix Version/s: 0.11.0
> Avoid access key started with -
> ---
>
> Key: PIO-54
> URL: https://issues.apache.org/jira/browse/PIO-54
> Project: PredictionIO
> Issue Type: Improvement
>Reporter: Shinsuke Sugaya
>Priority: Minor
> Fix For: 0.11.0
>
>
> Access key is generated by SecureRandom.
> If a key starts with -, it's difficult to use it as a command line argument.
> (I could not use it on data/import_eventserver.py...)
> {code}
> $ pio app list
> [INFO] [Pio$] Name | ID |
> Access Key | Allowed Event(s)
> [INFO] [Pio$] MyApp1 |1 |
> -vlfOdrcYDx1ZUXROcpSOQJDyTtrMMGkSEzyeHUSmGpmaP8s-GJoQl_Mm1YEQeGU | (all)
> [INFO] [Pio$] Finished listing 1 app(s).
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (PIO-30) Cross build for different versions of scala and spark
[ https://issues.apache.org/jira/browse/PIO-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto reassigned PIO-30: --- Assignee: Chan > Cross build for different versions of scala and spark > - > > Key: PIO-30 > URL: https://issues.apache.org/jira/browse/PIO-30 > Project: PredictionIO > Issue Type: Improvement >Reporter: Marcin Ziemiński >Assignee: Chan > Fix For: 0.11.0 > > > The present version of Scala is 2.10 and Spark is 1.4, which is quite old. > With Spark 2.0.0 come many performance improvements and features, that people > will definitely like to add to their templates. I am also aware that past > cannot be ignored and simply dumping 1.x might not be an option for other > users. > I propose setting up a crossbuild in sbt to build with scala 2.10 and Spark > 1.6 and a separate one for Scala 2.11 and Spark 2.0. Most of the files will > be consistent between versions including API. The problematic ones will be > divided between additional source directories: src/main/scala-2.10/ and > src/main/scala-2.11/. The dockerized tests should also take the two versions > into consideration -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-30) Cross build for different versions of scala and spark
[ https://issues.apache.org/jira/browse/PIO-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-30: Fix Version/s: 0.11.0 > Cross build for different versions of scala and spark > - > > Key: PIO-30 > URL: https://issues.apache.org/jira/browse/PIO-30 > Project: PredictionIO > Issue Type: Improvement >Reporter: Marcin Ziemiński >Assignee: Chan > Fix For: 0.11.0 > > > The present version of Scala is 2.10 and Spark is 1.4, which is quite old. > With Spark 2.0.0 come many performance improvements and features, that people > will definitely like to add to their templates. I am also aware that past > cannot be ignored and simply dumping 1.x might not be an option for other > users. > I propose setting up a crossbuild in sbt to build with scala 2.10 and Spark > 1.6 and a separate one for Scala 2.11 and Spark 2.0. Most of the files will > be consistent between versions including API. The problematic ones will be > divided between additional source directories: src/main/scala-2.10/ and > src/main/scala-2.11/. The dockerized tests should also take the two versions > into consideration -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-50) Change in repository link for template
[ https://issues.apache.org/jira/browse/PIO-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-50: Fix Version/s: (was: future release) 0.11.0 > Change in repository link for template > -- > > Key: PIO-50 > URL: https://issues.apache.org/jira/browse/PIO-50 > Project: PredictionIO > Issue Type: Improvement >Affects Versions: 0.10.0-incubating >Reporter: Bansari Shah > Fix For: 0.11.0 > > > changes in repository link. It is updated in templates.yaml for template: > Topic labelling with wikipedia. For this pull request is created #334 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-53) Create per-commit Docker image for testing
Donald Szeto created PIO-53: --- Summary: Create per-commit Docker image for testing Key: PIO-53 URL: https://issues.apache.org/jira/browse/PIO-53 Project: PredictionIO Issue Type: Test Reporter: Donald Szeto Assignee: Donald Szeto Fix For: 0.11.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (PIO-44) Developer API link on doc site is broken
[ https://issues.apache.org/jira/browse/PIO-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-44. - Resolution: Fixed Thanks [~chanlee514]! > Developer API link on doc site is broken > > > Key: PIO-44 > URL: https://issues.apache.org/jira/browse/PIO-44 > Project: PredictionIO > Issue Type: Bug >Reporter: Chan >Assignee: Chan > Fix For: 0.11.0 > > > http://predictionio.incubator.apache.org/api/current/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (PIO-44) Developer API link on doc site is broken
[ https://issues.apache.org/jira/browse/PIO-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto reassigned PIO-44: --- Assignee: Chan (was: Donald Szeto) > Developer API link on doc site is broken > > > Key: PIO-44 > URL: https://issues.apache.org/jira/browse/PIO-44 > Project: PredictionIO > Issue Type: Bug >Reporter: Chan >Assignee: Chan > Fix For: 0.11.0 > > > http://predictionio.incubator.apache.org/api/current/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (PIO-44) Developer API link on doc site is broken
[ https://issues.apache.org/jira/browse/PIO-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto reopened PIO-44: - The move to Apache Jenkins broke the link again. Please fix. > Developer API link on doc site is broken > > > Key: PIO-44 > URL: https://issues.apache.org/jira/browse/PIO-44 > Project: PredictionIO > Issue Type: Bug >Reporter: Chan >Assignee: Chan > Fix For: 0.11.0 > > > http://predictionio.incubator.apache.org/api/current/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-35) Add integration tests for major templates
[ https://issues.apache.org/jira/browse/PIO-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-35: Fix Version/s: 0.11.0 > Add integration tests for major templates > - > > Key: PIO-35 > URL: https://issues.apache.org/jira/browse/PIO-35 > Project: PredictionIO > Issue Type: Improvement >Reporter: Chan > Fix For: 0.11.0 > > > Developers of engine templates should be able to test that their template > works with the latest changes in PredictionIO. As a starting point, we can > expand the integration test suite to all previously "official" templates. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PIO-52) Misplaced Middleman frontmatter in documentation
Donald Szeto created PIO-52: --- Summary: Misplaced Middleman frontmatter in documentation Key: PIO-52 URL: https://issues.apache.org/jira/browse/PIO-52 Project: PredictionIO Issue Type: Bug Reporter: Donald Szeto Assignee: Donald Szeto Fix For: 0.11.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PIO-42) Negative Test Cases for Engine.train
[ https://issues.apache.org/jira/browse/PIO-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-42. - Resolution: Fixed Fix Version/s: (was: future release) 0.11.0 > Negative Test Cases for Engine.train > > > Key: PIO-42 > URL: https://issues.apache.org/jira/browse/PIO-42 > Project: PredictionIO > Issue Type: Test >Affects Versions: 0.10.0-incubating > Environment: All Envinronments >Reporter: Rajdeep Dua >Priority: Minor > Fix For: 0.11.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PIO-46) On BSD machines the pio command does not work
[ https://issues.apache.org/jira/browse/PIO-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-46. - Resolution: Fixed Fix Version/s: 0.11.0 > On BSD machines the pio command does not work > -- > > Key: PIO-46 > URL: https://issues.apache.org/jira/browse/PIO-46 > Project: PredictionIO > Issue Type: Bug >Affects Versions: 0.10.0-incubating > Environment: MacOS Sierra version 10.12.1 >Reporter: Takahiro Hagino > Fix For: 0.11.0 > > > Thanks for pio script's supporting soft link. > #289 https://github.com/apache/incubator-predictionio/pull/289 > But readlink -f doesn't seem to work on Mac and possibly BSD based systems. > As execute pio script, the following errors occurs. > ``` > readlink: illegal option -- f > usage: readlink [-n] [file ...] > usage: dirname path > bin/pio: line 45: //bin/pio-class: No such file or directory > bin/pio: line 45: exec: //bin/pio-class: cannot execute: No such file or > directory > ``` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PIO-40) Remove docs/manual/obsolete/*
[ https://issues.apache.org/jira/browse/PIO-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-40. - Resolution: Fixed > Remove docs/manual/obsolete/* > - > > Key: PIO-40 > URL: https://issues.apache.org/jira/browse/PIO-40 > Project: PredictionIO > Issue Type: Improvement >Affects Versions: 0.10.0-incubating >Reporter: Donald Szeto > Fix For: 0.11.0 > > > These are unmaintained and better be removed to avoid confusion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PIO-39) All *.md files are missing Apache License headers
[ https://issues.apache.org/jira/browse/PIO-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-39. - Resolution: Fixed > All *.md files are missing Apache License headers > - > > Key: PIO-39 > URL: https://issues.apache.org/jira/browse/PIO-39 > Project: PredictionIO > Issue Type: Improvement >Affects Versions: 0.10.0-incubating >Reporter: Donald Szeto >Assignee: Suneel Marthi > Fix For: 0.11.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PIO-34) Add Sentiment analysis and Topic Labelling template to PredictionIO gallary
[ https://issues.apache.org/jira/browse/PIO-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-34: Fix Version/s: (was: future release) 0.11.0 > Add Sentiment analysis and Topic Labelling template to PredictionIO gallary > --- > > Key: PIO-34 > URL: https://issues.apache.org/jira/browse/PIO-34 > Project: PredictionIO > Issue Type: New Feature >Affects Versions: 0.10.0-incubating >Reporter: Bansari Shah > Fix For: 0.11.0 > > > Adding sentiment analysis template that follows Bag of words model, build > with predictionIO-0.9.7-SNAPSHOT, scala - 2.10.6 and spark 1.5.1 with > predictionIO gallary > https://github.com/peoplehum/BagOfWords_SentimentAnalysis_Template/branches > Add Labelling LDA topics with wikipedia template with prdictionIO gallary > https://github.com/peoplehum/template-Labelling-LDA-Topics-with-wikipedia -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PIO-34) Add Sentiment analysis and Topic Labelling template to PredictionIO gallary
[ https://issues.apache.org/jira/browse/PIO-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-34. - Resolution: Fixed Assignee: Donald Szeto > Add Sentiment analysis and Topic Labelling template to PredictionIO gallary > --- > > Key: PIO-34 > URL: https://issues.apache.org/jira/browse/PIO-34 > Project: PredictionIO > Issue Type: New Feature >Affects Versions: 0.10.0-incubating >Reporter: Bansari Shah >Assignee: Donald Szeto > Fix For: 0.11.0 > > > Adding sentiment analysis template that follows Bag of words model, build > with predictionIO-0.9.7-SNAPSHOT, scala - 2.10.6 and spark 1.5.1 with > predictionIO gallary > https://github.com/peoplehum/BagOfWords_SentimentAnalysis_Template/branches > Add Labelling LDA topics with wikipedia template with prdictionIO gallary > https://github.com/peoplehum/template-Labelling-LDA-Topics-with-wikipedia -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PIO-43) Incorrect POM parent
[ https://issues.apache.org/jira/browse/PIO-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-43. - Resolution: Fixed > Incorrect POM parent > > > Key: PIO-43 > URL: https://issues.apache.org/jira/browse/PIO-43 > Project: PredictionIO > Issue Type: Bug >Affects Versions: 0.10.0-incubating >Reporter: Donald Szeto >Assignee: Donald Szeto > Fix For: 0.11.0 > > > The parent artifact in build.sbt is incorrect and causes engine template > builds to fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PIO-43) Incorrect POM parent
Donald Szeto created PIO-43: --- Summary: Incorrect POM parent Key: PIO-43 URL: https://issues.apache.org/jira/browse/PIO-43 Project: PredictionIO Issue Type: Bug Affects Versions: 0.10.0-incubating Reporter: Donald Szeto Assignee: Donald Szeto Fix For: 0.11.0 The parent artifact in build.sbt is incorrect and causes engine template builds to fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PIO-28) Extract logic from functions handling console commands in tools package.
[ https://issues.apache.org/jira/browse/PIO-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-28. - Resolution: Fixed > Extract logic from functions handling console commands in tools package. > > > Key: PIO-28 > URL: https://issues.apache.org/jira/browse/PIO-28 > Project: PredictionIO > Issue Type: Sub-task >Affects Versions: 0.10.0-incubating >Reporter: Marcin Ziemiński >Priority: Minor > Fix For: 0.11.0 > > > Currently functions used by Console.scala to handle commands are evaluated > for side effects - printing logs to the user. They either return integers or > units and sometimes use sys.exit(1) on failure. > The actual logic should be extracted from them to some other place for future > applications, e.g. to be used by admin server, which is not implemented yet. > Reporting results to the client should be separated from processing > application logic. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PIO-28) Extract logic from functions handling console commands in tools package.
[ https://issues.apache.org/jira/browse/PIO-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-28: Fix Version/s: 0.11.0 > Extract logic from functions handling console commands in tools package. > > > Key: PIO-28 > URL: https://issues.apache.org/jira/browse/PIO-28 > Project: PredictionIO > Issue Type: Sub-task >Affects Versions: 0.10.0-incubating >Reporter: Marcin Ziemiński >Priority: Minor > Fix For: 0.11.0 > > > Currently functions used by Console.scala to handle commands are evaluated > for side effects - printing logs to the user. They either return integers or > units and sometimes use sys.exit(1) on failure. > The actual logic should be extracted from them to some other place for future > applications, e.g. to be used by admin server, which is not implemented yet. > Reporting results to the client should be separated from processing > application logic. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PIO-40) Remove docs/manual/obsolete/*
Donald Szeto created PIO-40: --- Summary: Remove docs/manual/obsolete/* Key: PIO-40 URL: https://issues.apache.org/jira/browse/PIO-40 Project: PredictionIO Issue Type: Improvement Affects Versions: 0.10.0-incubating Reporter: Donald Szeto Fix For: 0.11.0 These are unmaintained and better be removed to avoid confusion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PIO-24) move templates to apache git repos
[ https://issues.apache.org/jira/browse/PIO-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-24: Fix Version/s: 0.10.1 > move templates to apache git repos > -- > > Key: PIO-24 > URL: https://issues.apache.org/jira/browse/PIO-24 > Project: PredictionIO > Issue Type: Task >Affects Versions: 0.10.0-incubating >Reporter: Pat Ferrel >Assignee: Pat Ferrel > Fix For: 0.10.1 > > > https://issues.apache.org/jira/browse/INFRA-12441 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PIO-7) document use of SSL
[ https://issues.apache.org/jira/browse/PIO-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-7: --- Fix Version/s: (was: 0.10.0) > document use of SSL > --- > > Key: PIO-7 > URL: https://issues.apache.org/jira/browse/PIO-7 > Project: PredictionIO > Issue Type: Sub-task >Reporter: Pat Ferrel >Assignee: Donald Szeto > > Document how to enable/disable SSL and manage certs, once pio-1 is ready -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PIO-22) Install.sh issues
[ https://issues.apache.org/jira/browse/PIO-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto updated PIO-22: Fix Version/s: (was: 0.10.0) > Install.sh issues > - > > Key: PIO-22 > URL: https://issues.apache.org/jira/browse/PIO-22 > Project: PredictionIO > Issue Type: Task >Reporter: Pat Ferrel > > The install.sh pushed with the AML merge has been re-worked to do a local > build of pio in all cases. This will work even for snapshots as long as there > is a tar.gz to download whereas the older method only worked on releases. > Not sure if we want to force source builds for releases so bringing this up > for discussion. > For one thing is would require a downloadable package, where we also could > use git and avoid the packaging of a source tar. For another we'd probably > like a non-source build version too. > Going back to a reversion is not ideal since the old install.sh misses > several important cases like installing postgres with es for templates like > the UR, which expect es. > Can anyone pick this up or comment? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PIO-37) install.sh script does not mkdir properly
[
https://issues.apache.org/jira/browse/PIO-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto resolved PIO-37.
-
Resolution: Fixed
Thanks for also making the easyfix and newbie tags!
> install.sh script does not mkdir properly
> -
>
> Key: PIO-37
> URL: https://issues.apache.org/jira/browse/PIO-37
> Project: PredictionIO
> Issue Type: Bug
> Environment: Ubuntu 15.10 x64
>Reporter: Aniruddha Adhikary
>Priority: Minor
> Labels: easyfix, newbie
>
> The install.sh script attempts to create ${vendors_dir} without creating it's
> parent; thus resulting in an error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (PIO-37) install.sh script does not mkdir properly
[
https://issues.apache.org/jira/browse/PIO-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Szeto updated PIO-37:
Fix Version/s: 0.10.0
> install.sh script does not mkdir properly
> -
>
> Key: PIO-37
> URL: https://issues.apache.org/jira/browse/PIO-37
> Project: PredictionIO
> Issue Type: Bug
> Environment: Ubuntu 15.10 x64
>Reporter: Aniruddha Adhikary
>Priority: Minor
> Labels: easyfix, newbie
> Fix For: 0.10.0
>
>
> The install.sh script attempts to create ${vendors_dir} without creating it's
> parent; thus resulting in an error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (PIO-6) Create doc site
[ https://issues.apache.org/jira/browse/PIO-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429866#comment-15429866 ] Donald Szeto edited comment on PIO-6 at 8/21/16 7:35 PM: - Before INFRA-12425 is resolved we can only perform manual pushes. I might find something to do so periodically. was (Author: dszeto): Before this issue is resolved we can only perform manual pushes. I might find something to do so periodically. > Create doc site > --- > > Key: PIO-6 > URL: https://issues.apache.org/jira/browse/PIO-6 > Project: PredictionIO > Issue Type: Task > Environment: Apache git pubsub docs site >Reporter: Pat Ferrel >Assignee: Donald Szeto > Fix For: 0.10.0 > > > create the pio site and start adding docs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
