[jira] [Commented] (PIO-185) Non-tracked Link in Apache Project page
[ https://issues.apache.org/jira/browse/PIO-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665613#comment-16665613 ] Wei Chen commented on PIO-185: -- >From what I am seeing here, the link on >[https://projects.apache.org/project.html?predictionio] haven't changed yet. Let's wait for a day to see if it will be changed automatically. > Non-tracked Link in Apache Project page > --- > > Key: PIO-185 > URL: https://issues.apache.org/jira/browse/PIO-185 > Project: PredictionIO > Issue Type: Bug > Components: Documentation >Reporter: Wei Chen >Assignee: Wei Chen >Priority: Minor > Fix For: Live Documentation, 0.14.0 > > > On page: [https://projects.apache.org/project.html?predictionio] > at line 15: > -> *Git repository:* > [https://git-wip-us.apache.org/repos/asf/predictionio.git] > There is no git repo with the link. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PIO-182) Add asynchronous (non-blocking) methods to LEventStore
[
https://issues.apache.org/jira/browse/PIO-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665532#comment-16665532
]
ASF GitHub Bot commented on PIO-182:
dszeto commented on issue #482: [PIO-182] Add async methods to LEventStore
URL: https://github.com/apache/predictionio/pull/482#issuecomment-433506092
How about we push for deprecating blocking methods? We can update docs to
instruct developers to start using non-blocking methods instead.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add asynchronous (non-blocking) methods to LEventStore
> --
>
> Key: PIO-182
> URL: https://issues.apache.org/jira/browse/PIO-182
> Project: PredictionIO
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.13.0
>Reporter: Naoki Takezoe
>Assignee: Naoki Takezoe
>Priority: Major
>
> The current implementation of {{LEventStore}} has only synchronous (blocking)
> methods. Since they use {{ExecutionContext.Implicit.global}}, its parallelism
> is limited up to the number of processors. This means engine server's
> parallelism is also limited if we use these methods in prediction logic.
> To solve this problem, {{Future}} version of these methods should be added to
> {{LEventStore}} and also current blocking methods should be modified to take
> {{ExecutionContext}} (as an implicit parameter).
> See also:
> https://lists.apache.org/thread.html/f14e4f8f29410e4585b3d8e9f646b88293a605f4716d3c4d60771854@%3Cuser.predictionio.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PIO-182) Add asynchronous (non-blocking) methods to LEventStore
[
https://issues.apache.org/jira/browse/PIO-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665525#comment-16665525
]
ASF GitHub Bot commented on PIO-182:
dszeto commented on a change in pull request #482: [PIO-182] Add async methods
to LEventStore
URL: https://github.com/apache/predictionio/pull/482#discussion_r228627635
##
File path:
data/src/main/scala/org/apache/predictionio/data/store/LEventStore.scala
##
@@ -20,15 +20,27 @@ package org.apache.predictionio.data.store
import org.apache.predictionio.data.storage.Storage
import org.apache.predictionio.data.storage.Event
-
import org.joda.time.DateTime
-import scala.concurrent.Await
-import scala.concurrent.ExecutionContext.Implicits.global
+import scala.concurrent.{Await, ExecutionContext, Future}
import scala.concurrent.duration.Duration
/** This object provides a set of operation to access Event Store
- * without going through Spark's parallelization
+ * without going through Spark's parallelization.
+ *
+ * Note that blocking methods of this object uses
+ * `scala.concurrent.ExecutionContext.Implicits.global` internally.
+ * Since this is a thread pool which has a number of threads equal to
available
+ * processors, parallelism is limited up to the number of processors.
+ *
+ * If this limitation become bottleneck of resource usage, you can increase
the
+ * number of threads by declaring following VM options before calling "pio
deploy":
+ *
+ *
+ * export JAVA_OPTS="$JAVA_OPTS \
+ * -Dscala.concurrent.context.numThreads=1000 \
+ * -Dscala.concurrent.context.maxThreads=1000"
+ *
Review comment:
LGTM. We can link to
https://docs.scala-lang.org/overviews/core/futures.html#the-global-execution-context
for a detail explanation if you'd like to.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add asynchronous (non-blocking) methods to LEventStore
> --
>
> Key: PIO-182
> URL: https://issues.apache.org/jira/browse/PIO-182
> Project: PredictionIO
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.13.0
>Reporter: Naoki Takezoe
>Assignee: Naoki Takezoe
>Priority: Major
>
> The current implementation of {{LEventStore}} has only synchronous (blocking)
> methods. Since they use {{ExecutionContext.Implicit.global}}, its parallelism
> is limited up to the number of processors. This means engine server's
> parallelism is also limited if we use these methods in prediction logic.
> To solve this problem, {{Future}} version of these methods should be added to
> {{LEventStore}} and also current blocking methods should be modified to take
> {{ExecutionContext}} (as an implicit parameter).
> See also:
> https://lists.apache.org/thread.html/f14e4f8f29410e4585b3d8e9f646b88293a605f4716d3c4d60771854@%3Cuser.predictionio.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (PIO-188) Update the build matrix to the latest supported versions
[ https://issues.apache.org/jira/browse/PIO-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-188. -- Resolution: Fixed Assignee: Takako Shimamoto Fix Version/s: 0.14.0 > Update the build matrix to the latest supported versions > > > Key: PIO-188 > URL: https://issues.apache.org/jira/browse/PIO-188 > Project: PredictionIO > Issue Type: Improvement > Components: Build, Documentation >Affects Versions: 0.14.0 >Reporter: Takako Shimamoto >Assignee: Takako Shimamoto >Priority: Major > Fix For: 0.14.0 > > > At first glance, it looks like .travis.yml has covered every version, but > there aren't tests for Elasticsearch 6.x or HBase 1.2 currently. Whereas that > there are some unnecessary patterns in the build matrix. > I put together the latest supported versions. Note that there is no change in > the default version. > h3. Core versions > - Scala > -- 2.11.12(default) > - Spark > -- 2.0.2 > -- 2.1.3(default) > -- 2.2.2 > -- 2.3.2 > - Hadoop > -- 2.6.5 > -- 2.7.3(default) > h3. Storage versions > - Elasticsearch > -- 1.7.3(deprecated) > -- 5.6.9(default) > -- 6.4.2 > - HBase > -- 1.2.6(default) > - HDFS > -- same as above Hadoop > I will open a PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PIO-188) Update the build matrix to the latest supported versions
[ https://issues.apache.org/jira/browse/PIO-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665520#comment-16665520 ] ASF GitHub Bot commented on PIO-188: dszeto commented on issue #489: [PIO-188] Update the build matrix on travis URL: https://github.com/apache/predictionio/pull/489#issuecomment-433503339 Thanks for cleaning up the cross build @shimamoto ! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Update the build matrix to the latest supported versions > > > Key: PIO-188 > URL: https://issues.apache.org/jira/browse/PIO-188 > Project: PredictionIO > Issue Type: Improvement > Components: Build, Documentation >Affects Versions: 0.14.0 >Reporter: Takako Shimamoto >Priority: Major > > At first glance, it looks like .travis.yml has covered every version, but > there aren't tests for Elasticsearch 6.x or HBase 1.2 currently. Whereas that > there are some unnecessary patterns in the build matrix. > I put together the latest supported versions. Note that there is no change in > the default version. > h3. Core versions > - Scala > -- 2.11.12(default) > - Spark > -- 2.0.2 > -- 2.1.3(default) > -- 2.2.2 > -- 2.3.2 > - Hadoop > -- 2.6.5 > -- 2.7.3(default) > h3. Storage versions > - Elasticsearch > -- 1.7.3(deprecated) > -- 5.6.9(default) > -- 6.4.2 > - HBase > -- 1.2.6(default) > - HDFS > -- same as above Hadoop > I will open a PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PIO-186) Github description update spray to akka-http
[ https://issues.apache.org/jira/browse/PIO-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665511#comment-16665511 ] Donald Szeto commented on PIO-186: -- An INFRA ticket is needed to fulfill this, since none of us have admin access to the GitHub mirror. > Github description update spray to akka-http > > > Key: PIO-186 > URL: https://issues.apache.org/jira/browse/PIO-186 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Reporter: Wei Chen >Priority: Minor > > In our Github page: https://github.com/apache/predictionio > In the project description (the line on top of the status bar) > We see: > *PredictionIO, a machine learning server for developers and ML engineers. > Built on Apache Spark, HBase and Spray.* > which should be updated from *Spray* to *Akka-Http* > *PredictionIO, a machine learning server for developers and ML engineers. > Built on Apache Spark, HBase, and Akka-Http.* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PIO-187) Livedoc and Develop-Readme Docker Doc Update
[ https://issues.apache.org/jira/browse/PIO-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Chen updated PIO-187: - Summary: Livedoc and Develop-Readme Docker Doc Update (was: Livedoc and Develop-Readme Official Docker Doc Update) > Livedoc and Develop-Readme Docker Doc Update > > > Key: PIO-187 > URL: https://issues.apache.org/jira/browse/PIO-187 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Affects Versions: Future, Live Documentation >Reporter: Wei Chen >Assignee: Wei Chen >Priority: Minor > Fix For: Future, Live Documentation > > > Official Docker support had been provided through > [#462|https://github.com/apache/predictionio/pull/462] > Based on the discussion with [~shinsuke] in PIO-86 > We create another issue to track the modification of livedoc and develop > readme. > In this issue: > 1. Create a new official Docker installation page in livedoc > 2. Modify the Docker installation link in livedoc and develop readme -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PIO-187) Livedoc and Develop-Readme Docker Doc Update
[ https://issues.apache.org/jira/browse/PIO-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Chen updated PIO-187: - Description: Docker support had been provided through [#462|https://github.com/apache/predictionio/pull/462] Based on the discussion with [~shinsuke] in PIO-86 We create another issue to track the modification of livedoc and develop readme. In this issue: 1. Create a new Docker installation page in livedoc 2. Modify the Docker installation link in livedoc and develop readme was: Official Docker support had been provided through [#462|https://github.com/apache/predictionio/pull/462] Based on the discussion with [~shinsuke] in PIO-86 We create another issue to track the modification of livedoc and develop readme. In this issue: 1. Create a new official Docker installation page in livedoc 2. Modify the Docker installation link in livedoc and develop readme > Livedoc and Develop-Readme Docker Doc Update > > > Key: PIO-187 > URL: https://issues.apache.org/jira/browse/PIO-187 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Affects Versions: Future, Live Documentation >Reporter: Wei Chen >Assignee: Wei Chen >Priority: Minor > Fix For: Future, Live Documentation > > > Docker support had been provided through > [#462|https://github.com/apache/predictionio/pull/462] > Based on the discussion with [~shinsuke] in PIO-86 > We create another issue to track the modification of livedoc and develop > readme. > In this issue: > 1. Create a new Docker installation page in livedoc > 2. Modify the Docker installation link in livedoc and develop readme -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PIO-187) Livedoc and Develop-Readme Official Docker Doc Update
[ https://issues.apache.org/jira/browse/PIO-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665457#comment-16665457 ] ASF GitHub Bot commented on PIO-187: Wei-1 commented on a change in pull request #486: [PIO-187] Livedoc with Docker Installation Update URL: https://github.com/apache/predictionio/pull/486#discussion_r228612000 ## File path: docs/manual/source/install/install-docker.html.md.erb ## @@ -21,22 +21,34 @@ limitations under the License. ## Download and Start Docker -Docker is a widely used container solution. Please download and start Docker by following their [official guide](https://www.docker.com/get-started). +Docker is a widely used container solution. Please download and start Docker by following their [guide](https://www.docker.com/get-started). ## Get PredictionIO and Dependencies Configuration -Starting from v0.13.0, Apache PredictionIO® starts to provide official docker support for production environment. `Dockerfile` and dependencies configuration can be found in the `docker` folder in the [git repository](https://github.com/apache/predictionio/tree/develop/docker). +Starting from v0.13.0, Apache PredictionIO® starts to provide docker support for the production environment. `Dockerfile` and dependencies configuration can be found in the `docker` folder in the [git repository](https://github.com/apache/predictionio/tree/develop/docker). ```bash git clone https://github.com/apache/predictionio.git cd predictionio/docker ``` -INFO: In this installation, we only need the `docker` sub-directory in the repository. One can use other tools to get the folder without cloning the whole preject. +INFO: In this installation, we only need the `docker` sub-directory in the repository. One can use other tools to get the folder without cloning the whole project. -## Pull Images and Start +## Build Docker Image + +To build PredictionIO docker image, `Dockerfile` is provided in sub-directory `pio`. + +``` +docker build -t predictionio/pio pio +``` + +One will be able to build an image with tag `prediction/pio:latest` using the above command. + +WARNING: People can get PredictionIO image from Dockerhub through `docker pull predictionio/pio`. However, since the image cannot run without a properly configured storage, please follow the following steps to complete the installation. + +WARNING: Image `prediction/pio` hosted on Dockerhub is **NOT** regarded as an official ASF release and might provide a different PredictionIO version from your desired PredictionIO version. It is recommended to build the image locally other than pulling directly from Dockerhub. Review comment: Agree. Currently, the image on Dockerhub is 0.12.1, which is different from the 0.13.0 that we are trying to target. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Livedoc and Develop-Readme Official Docker Doc Update > - > > Key: PIO-187 > URL: https://issues.apache.org/jira/browse/PIO-187 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Affects Versions: Future, Live Documentation >Reporter: Wei Chen >Assignee: Wei Chen >Priority: Minor > Fix For: Future, Live Documentation > > > Official Docker support had been provided through > [#462|https://github.com/apache/predictionio/pull/462] > Based on the discussion with [~shinsuke] in PIO-86 > We create another issue to track the modification of livedoc and develop > readme. > In this issue: > 1. Create a new official Docker installation page in livedoc > 2. Modify the Docker installation link in livedoc and develop readme -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PIO-187) Livedoc and Develop-Readme Official Docker Doc Update
[ https://issues.apache.org/jira/browse/PIO-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665456#comment-16665456 ] ASF GitHub Bot commented on PIO-187: dszeto commented on issue #486: [PIO-187] Livedoc with Docker Installation Update URL: https://github.com/apache/predictionio/pull/486#issuecomment-433489310 LGTM. @marevol do you want to take a second look? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Livedoc and Develop-Readme Official Docker Doc Update > - > > Key: PIO-187 > URL: https://issues.apache.org/jira/browse/PIO-187 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Affects Versions: Future, Live Documentation >Reporter: Wei Chen >Assignee: Wei Chen >Priority: Minor > Fix For: Future, Live Documentation > > > Official Docker support had been provided through > [#462|https://github.com/apache/predictionio/pull/462] > Based on the discussion with [~shinsuke] in PIO-86 > We create another issue to track the modification of livedoc and develop > readme. > In this issue: > 1. Create a new official Docker installation page in livedoc > 2. Modify the Docker installation link in livedoc and develop readme -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PIO-187) Livedoc and Develop-Readme Official Docker Doc Update
[ https://issues.apache.org/jira/browse/PIO-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665455#comment-16665455 ] ASF GitHub Bot commented on PIO-187: dszeto commented on a change in pull request #486: [PIO-187] Livedoc with Docker Installation Update URL: https://github.com/apache/predictionio/pull/486#discussion_r228611568 ## File path: docs/manual/source/install/install-docker.html.md.erb ## @@ -21,22 +21,34 @@ limitations under the License. ## Download and Start Docker -Docker is a widely used container solution. Please download and start Docker by following their [official guide](https://www.docker.com/get-started). +Docker is a widely used container solution. Please download and start Docker by following their [guide](https://www.docker.com/get-started). ## Get PredictionIO and Dependencies Configuration -Starting from v0.13.0, Apache PredictionIO® starts to provide official docker support for production environment. `Dockerfile` and dependencies configuration can be found in the `docker` folder in the [git repository](https://github.com/apache/predictionio/tree/develop/docker). +Starting from v0.13.0, Apache PredictionIO® starts to provide docker support for the production environment. `Dockerfile` and dependencies configuration can be found in the `docker` folder in the [git repository](https://github.com/apache/predictionio/tree/develop/docker). ```bash git clone https://github.com/apache/predictionio.git cd predictionio/docker ``` -INFO: In this installation, we only need the `docker` sub-directory in the repository. One can use other tools to get the folder without cloning the whole preject. +INFO: In this installation, we only need the `docker` sub-directory in the repository. One can use other tools to get the folder without cloning the whole project. -## Pull Images and Start +## Build Docker Image + +To build PredictionIO docker image, `Dockerfile` is provided in sub-directory `pio`. + +``` +docker build -t predictionio/pio pio +``` + +One will be able to build an image with tag `prediction/pio:latest` using the above command. + +WARNING: People can get PredictionIO image from Dockerhub through `docker pull predictionio/pio`. However, since the image cannot run without a properly configured storage, please follow the following steps to complete the installation. + +WARNING: Image `prediction/pio` hosted on Dockerhub is **NOT** regarded as an official ASF release and might provide a different PredictionIO version from your desired PredictionIO version. It is recommended to build the image locally other than pulling directly from Dockerhub. Review comment: We should tag Docker images with version as a separate work item. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Livedoc and Develop-Readme Official Docker Doc Update > - > > Key: PIO-187 > URL: https://issues.apache.org/jira/browse/PIO-187 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Affects Versions: Future, Live Documentation >Reporter: Wei Chen >Assignee: Wei Chen >Priority: Minor > Fix For: Future, Live Documentation > > > Official Docker support had been provided through > [#462|https://github.com/apache/predictionio/pull/462] > Based on the discussion with [~shinsuke] in PIO-86 > We create another issue to track the modification of livedoc and develop > readme. > In this issue: > 1. Create a new official Docker installation page in livedoc > 2. Modify the Docker installation link in livedoc and develop readme -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PIO-187) Livedoc and Develop-Readme Official Docker Doc Update
[ https://issues.apache.org/jira/browse/PIO-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665453#comment-16665453 ] ASF GitHub Bot commented on PIO-187: Wei-1 commented on a change in pull request #486: [PIO-187] Livedoc with Docker Installation Update URL: https://github.com/apache/predictionio/pull/486#discussion_r228611459 ## File path: docs/manual/source/install/install-docker.html.md.erb ## @@ -0,0 +1,127 @@ +--- +title: Installing Apache PredictionIO® with Docker +--- + + + +## Download and Start Docker + +Docker is a widely used container solution. Please download and start Docker by following their [guide](https://www.docker.com/get-started). + +## Get PredictionIO and Dependencies Configuration + +Starting from v0.13.0, Apache PredictionIO® starts to provide docker support for the production environment. `Dockerfile` and dependencies configuration can be found in the `docker` folder in the [git repository](https://github.com/apache/predictionio/tree/develop/docker). + +```bash +git clone https://github.com/apache/predictionio.git +cd predictionio/docker +``` + +INFO: In this installation, we only need the `docker` sub-directory in the repository. One can use other tools to get the folder without cloning the whole project. + +## Build Docker Image + +To build PredictionIO docker image, `Dockerfile` is provided in sub-directory `pio`. + +``` +docker build -t predictionio/pio pio +``` + +One will be able to build an image with tag `prediction/pio:latest` using the above command. + +WARNING: People can get PredictionIO image from Dockerhub through `docker pull predictionio/pio`. However, since the image cannot run without a properly configured storage, please follow the following steps to complete the installation. + +WARNING: Image `prediction/pio` hosted on Dockerhub is **NOT** regarded as an official ASF release and might provide a different PredictionIO version from your desired PredictionIO version. It is recommended to build the image locally other than pulling directly from Dockerhub. Review comment: @dszeto how about this? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Livedoc and Develop-Readme Official Docker Doc Update > - > > Key: PIO-187 > URL: https://issues.apache.org/jira/browse/PIO-187 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Affects Versions: Future, Live Documentation >Reporter: Wei Chen >Assignee: Wei Chen >Priority: Minor > Fix For: Future, Live Documentation > > > Official Docker support had been provided through > [#462|https://github.com/apache/predictionio/pull/462] > Based on the discussion with [~shinsuke] in PIO-86 > We create another issue to track the modification of livedoc and develop > readme. > In this issue: > 1. Create a new official Docker installation page in livedoc > 2. Modify the Docker installation link in livedoc and develop readme -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PIO-187) Livedoc and Develop-Readme Official Docker Doc Update
[ https://issues.apache.org/jira/browse/PIO-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665422#comment-16665422 ] ASF GitHub Bot commented on PIO-187: Wei-1 commented on issue #486: [PIO-187] Livedoc with Docker Installation Update URL: https://github.com/apache/predictionio/pull/486#issuecomment-433477136 @dszeto, I will modify it for sure. thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Livedoc and Develop-Readme Official Docker Doc Update > - > > Key: PIO-187 > URL: https://issues.apache.org/jira/browse/PIO-187 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Affects Versions: Future, Live Documentation >Reporter: Wei Chen >Assignee: Wei Chen >Priority: Minor > Fix For: Future, Live Documentation > > > Official Docker support had been provided through > [#462|https://github.com/apache/predictionio/pull/462] > Based on the discussion with [~shinsuke] in PIO-86 > We create another issue to track the modification of livedoc and develop > readme. > In this issue: > 1. Create a new official Docker installation page in livedoc > 2. Modify the Docker installation link in livedoc and develop readme -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PIO-187) Livedoc and Develop-Readme Official Docker Doc Update
[ https://issues.apache.org/jira/browse/PIO-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665413#comment-16665413 ] ASF GitHub Bot commented on PIO-187: dszeto commented on issue #486: [PIO-187] Livedoc with Docker Installation Update URL: https://github.com/apache/predictionio/pull/486#issuecomment-433474510 Thanks for writing this up! One small request: we have to declare that any Docker container image published to Docker Hub be **not official ASF releases**. Those can only be referred to as convenience binaries. We can say that the Docker build files in our Git repo as official though. For more information please refer to http://www.apache.org/legal/release-policy.html. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Livedoc and Develop-Readme Official Docker Doc Update > - > > Key: PIO-187 > URL: https://issues.apache.org/jira/browse/PIO-187 > Project: PredictionIO > Issue Type: Improvement > Components: Documentation >Affects Versions: Future, Live Documentation >Reporter: Wei Chen >Assignee: Wei Chen >Priority: Minor > Fix For: Future, Live Documentation > > > Official Docker support had been provided through > [#462|https://github.com/apache/predictionio/pull/462] > Based on the discussion with [~shinsuke] in PIO-86 > We create another issue to track the modification of livedoc and develop > readme. > In this issue: > 1. Create a new official Docker installation page in livedoc > 2. Modify the Docker installation link in livedoc and develop readme -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (PIO-185) Non-tracked Link in Apache Project page
[ https://issues.apache.org/jira/browse/PIO-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Szeto resolved PIO-185. -- Resolution: Fixed Fix Version/s: 0.14.0 Live Documentation > Non-tracked Link in Apache Project page > --- > > Key: PIO-185 > URL: https://issues.apache.org/jira/browse/PIO-185 > Project: PredictionIO > Issue Type: Bug > Components: Documentation >Reporter: Wei Chen >Assignee: Wei Chen >Priority: Minor > Fix For: Live Documentation, 0.14.0 > > > On page: [https://projects.apache.org/project.html?predictionio] > at line 15: > -> *Git repository:* > [https://git-wip-us.apache.org/repos/asf/predictionio.git] > There is no git repo with the link. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PIO-185) Non-tracked Link in Apache Project page
[ https://issues.apache.org/jira/browse/PIO-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665398#comment-16665398 ] ASF GitHub Bot commented on PIO-185: dszeto commented on issue #485: [PIO-185] develop Gitbox link Update URL: https://github.com/apache/predictionio/pull/485#issuecomment-433470774 Sorry for the late reply. Thanks @Wei-1 ! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Non-tracked Link in Apache Project page > --- > > Key: PIO-185 > URL: https://issues.apache.org/jira/browse/PIO-185 > Project: PredictionIO > Issue Type: Bug > Components: Documentation >Reporter: Wei Chen >Assignee: Wei Chen >Priority: Minor > > On page: [https://projects.apache.org/project.html?predictionio] > at line 15: > -> *Git repository:* > [https://git-wip-us.apache.org/repos/asf/predictionio.git] > There is no git repo with the link. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (PIO-185) Non-tracked Link in Apache Project page
[
https://issues.apache.org/jira/browse/PIO-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665399#comment-16665399
]
ASF GitHub Bot commented on PIO-185:
dszeto closed pull request #485: [PIO-185] develop Gitbox link Update
URL: https://github.com/apache/predictionio/pull/485
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/build.sbt b/build.sbt
index 2a6204215..94739ff25 100644
--- a/build.sbt
+++ b/build.sbt
@@ -277,7 +277,7 @@ pomExtra := {
scm:git:github.com/apache/predictionio
-
scm:git:https://git-wip-us.apache.org/repos/asf/predictionio.git
+
scm:git:https://gitbox.apache.org/repos/asf/predictionio.git
github.com/apache/predictionio
diff --git a/doap.rdf b/doap.rdf
index 26f430fc1..05519782f 100644
--- a/doap.rdf
+++ b/doap.rdf
@@ -35,8 +35,8 @@
http://projects.apache.org/category/big-data; />
-https://git-wip-us.apache.org/repos/asf/predictionio.git"/>
-https://git-wip-us.apache.org/repos/asf/predictionio.git"/>
+https://gitbox.apache.org/repos/asf/predictionio.git"/>
+https://gitbox.apache.org/repos/asf/predictionio.git"/>
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Non-tracked Link in Apache Project page
> ---
>
> Key: PIO-185
> URL: https://issues.apache.org/jira/browse/PIO-185
> Project: PredictionIO
> Issue Type: Bug
> Components: Documentation
>Reporter: Wei Chen
>Assignee: Wei Chen
>Priority: Minor
>
> On page: [https://projects.apache.org/project.html?predictionio]
> at line 15:
> -> *Git repository:*
> [https://git-wip-us.apache.org/repos/asf/predictionio.git]
> There is no git repo with the link.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PIO-182) Add asynchronous (non-blocking) methods to LEventStore
[
https://issues.apache.org/jira/browse/PIO-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665020#comment-16665020
]
ASF GitHub Bot commented on PIO-182:
takezoe edited a comment on issue #482: [PIO-182] Add async methods to
LEventStore
URL: https://github.com/apache/predictionio/pull/482#issuecomment-433363303
@longliveenduro Using the default execution context in this pull request is
just for backward compatibility with the current blocking methods. Making it
configurable might be better, but we can increase the number of threads by
giving a VM option. I think it's a sufficient workaround.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add asynchronous (non-blocking) methods to LEventStore
> --
>
> Key: PIO-182
> URL: https://issues.apache.org/jira/browse/PIO-182
> Project: PredictionIO
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.13.0
>Reporter: Naoki Takezoe
>Assignee: Naoki Takezoe
>Priority: Major
>
> The current implementation of {{LEventStore}} has only synchronous (blocking)
> methods. Since they use {{ExecutionContext.Implicit.global}}, its parallelism
> is limited up to the number of processors. This means engine server's
> parallelism is also limited if we use these methods in prediction logic.
> To solve this problem, {{Future}} version of these methods should be added to
> {{LEventStore}} and also current blocking methods should be modified to take
> {{ExecutionContext}} (as an implicit parameter).
> See also:
> https://lists.apache.org/thread.html/f14e4f8f29410e4585b3d8e9f646b88293a605f4716d3c4d60771854@%3Cuser.predictionio.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PIO-182) Add asynchronous (non-blocking) methods to LEventStore
[
https://issues.apache.org/jira/browse/PIO-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16664990#comment-16664990
]
ASF GitHub Bot commented on PIO-182:
takezoe commented on issue #482: [PIO-182] Add async methods to LEventStore
URL: https://github.com/apache/predictionio/pull/482#issuecomment-433363303
@longliveenduro Using of the default execution context in this pull request
is just for backward compatibility with the current blocking methods. Making it
configurable might be better, but we can increase the number of threads by
giving a VM option. I think it's a sufficient workaround.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add asynchronous (non-blocking) methods to LEventStore
> --
>
> Key: PIO-182
> URL: https://issues.apache.org/jira/browse/PIO-182
> Project: PredictionIO
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.13.0
>Reporter: Naoki Takezoe
>Assignee: Naoki Takezoe
>Priority: Major
>
> The current implementation of {{LEventStore}} has only synchronous (blocking)
> methods. Since they use {{ExecutionContext.Implicit.global}}, its parallelism
> is limited up to the number of processors. This means engine server's
> parallelism is also limited if we use these methods in prediction logic.
> To solve this problem, {{Future}} version of these methods should be added to
> {{LEventStore}} and also current blocking methods should be modified to take
> {{ExecutionContext}} (as an implicit parameter).
> See also:
> https://lists.apache.org/thread.html/f14e4f8f29410e4585b3d8e9f646b88293a605f4716d3c4d60771854@%3Cuser.predictionio.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PIO-182) Add asynchronous (non-blocking) methods to LEventStore
[
https://issues.apache.org/jira/browse/PIO-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16664982#comment-16664982
]
ASF GitHub Bot commented on PIO-182:
longliveenduro commented on issue #482: [PIO-182] Add async methods to
LEventStore
URL: https://github.com/apache/predictionio/pull/482#issuecomment-433360671
@takezoe yes exactly, seperate Threadpools for CPU and I/O bound blocking
processing looks like a very good idea for a transition phase. Also looking at
the Blogs they suggest a fixed Threadpool instead of a ForkJoin Threadpool
(which the "standard" Scala thread pool is) for blocking I/O code.
Anyhow, looking at your PR, you are importing the standard Scala execution
context in the methods that still use blocking via Await.result. What about
using a separate Threadpool there whose size is either configurable or you pass
it as a parameter. Passing as a parameter though is breaking the current
contract and is a little bit strange since the method does not return an async
instance (e.g. Future) which I would expect from a scala method which needs an
ExecutionContext param.
Very interested what you think!
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add asynchronous (non-blocking) methods to LEventStore
> --
>
> Key: PIO-182
> URL: https://issues.apache.org/jira/browse/PIO-182
> Project: PredictionIO
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.13.0
>Reporter: Naoki Takezoe
>Assignee: Naoki Takezoe
>Priority: Major
>
> The current implementation of {{LEventStore}} has only synchronous (blocking)
> methods. Since they use {{ExecutionContext.Implicit.global}}, its parallelism
> is limited up to the number of processors. This means engine server's
> parallelism is also limited if we use these methods in prediction logic.
> To solve this problem, {{Future}} version of these methods should be added to
> {{LEventStore}} and also current blocking methods should be modified to take
> {{ExecutionContext}} (as an implicit parameter).
> See also:
> https://lists.apache.org/thread.html/f14e4f8f29410e4585b3d8e9f646b88293a605f4716d3c4d60771854@%3Cuser.predictionio.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (PIO-189) ES6 integration test fails
[ https://issues.apache.org/jira/browse/PIO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takako Shimamoto resolved PIO-189. -- Resolution: Fixed > ES6 integration test fails > -- > > Key: PIO-189 > URL: https://issues.apache.org/jira/browse/PIO-189 > Project: PredictionIO > Issue Type: Sub-task > Components: Core >Reporter: Takako Shimamoto >Assignee: Alexander Merritt >Priority: Major > Fix For: 0.14.0 > > > ES6 integration test fails when > PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=ELASTICSEARCH is specified. > https://travis-ci.org/apache/predictionio/builds/445535291 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (PIO-189) ES6 integration test fails
[ https://issues.apache.org/jira/browse/PIO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takako Shimamoto reassigned PIO-189: Assignee: Alexander Merritt > ES6 integration test fails > -- > > Key: PIO-189 > URL: https://issues.apache.org/jira/browse/PIO-189 > Project: PredictionIO > Issue Type: Sub-task > Components: Core >Reporter: Takako Shimamoto >Assignee: Alexander Merritt >Priority: Major > Fix For: 0.14.0 > > > ES6 integration test fails when > PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=ELASTICSEARCH is specified. > https://travis-ci.org/apache/predictionio/builds/445535291 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PIO-189) ES6 integration test fails
[ https://issues.apache.org/jira/browse/PIO-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takako Shimamoto updated PIO-189: - Fix Version/s: 0.14.0 > ES6 integration test fails > -- > > Key: PIO-189 > URL: https://issues.apache.org/jira/browse/PIO-189 > Project: PredictionIO > Issue Type: Sub-task > Components: Core >Reporter: Takako Shimamoto >Assignee: Alexander Merritt >Priority: Major > Fix For: 0.14.0 > > > ES6 integration test fails when > PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=ELASTICSEARCH is specified. > https://travis-ci.org/apache/predictionio/builds/445535291 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
