[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16025891#comment-16025891
]
ASF GitHub Bot commented on PIO-72:
---
GitHub user chanlee514 opened a pull request:
https://github.com/apache/incubator-predictionio/pull/385
[PIO-72] Fix class loading for pio-shell
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chanlee514/incubator-predictionio develop
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-predictionio/pull/385.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #385
commit ab89fbc10e72887b4a5abc0914e1ed414c5c3f1f
Author: Chan Lee
Date: 2017-05-26T06:22:47Z
[PIO-72] Fix class loading for pio-shell
> 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
> 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:6
Re: JIRA and release process for PredictionIO
+1 On Thu, May 25, 2017 at 9:20 PM, Sara Asher wrote: > Hi everyone, > > It looks like everyone is content with the JIRA/release process doc. If I > don't hear from anyone else in the next day or so, I will assume it's good > and will add the details to the public documentation for PredictionIO. > > Thanks, > Sara > > On Thu, May 18, 2017 at 1:30 PM, Donald Szeto wrote: > > > +1. Thanks Sara! > > > > On Thu, May 18, 2017 at 8:48 AM Sara Asher wrote: > > > > > Hi everyone, > > > > > > Thank you for allowing me to join the PredictionIO team! > > > > > > To start with, I would like to document a process for using JIRA and to > > > suggest a standard release cadence for PredictionIO. > > > > > > I've worked with Donald to come up with the following: > > > > > > https://docs.google.com/document/d/1nQpENncXZq72KeI3WMe_ > > > X8Xz8HKkYO2QC12GD3ZKP9g/edit?usp=sharing > > > > > > Please comment and give suggestions! When you are all content, I will > > add > > > this to our public documentation. > > > > > > Thanks, > > > Sara > > > > > >
[jira] [Updated] (PIO-86) Maintain a working docker container
[ https://issues.apache.org/jira/browse/PIO-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-86: -- Target Version/s: 0.12.0-incubating > Maintain a working docker container > --- > > Key: PIO-86 > URL: https://issues.apache.org/jira/browse/PIO-86 > Project: PredictionIO > Issue Type: Wish >Reporter: Sara Asher > Labels: needs-discussion > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-87) Fix doc licensing issues
[ https://issues.apache.org/jira/browse/PIO-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-87: -- Target Version/s: 0.12.0-incubating Fix Version/s: (was: 0.12.0-incubating) > Fix doc licensing issues > > > Key: PIO-87 > URL: https://issues.apache.org/jira/browse/PIO-87 > Project: PredictionIO > Issue Type: Bug >Reporter: Sara Asher > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-69) Create binary version of PredictionIO as part of release process
[ https://issues.apache.org/jira/browse/PIO-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-69: -- Target Version/s: 0.12.0-incubating > Create binary version of PredictionIO as part of release process > > > Key: PIO-69 > URL: https://issues.apache.org/jira/browse/PIO-69 > Project: PredictionIO > Issue Type: New Feature > Components: Build >Reporter: Sara Asher > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-88) Scripts for Windows
[ https://issues.apache.org/jira/browse/PIO-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-88: -- Description: Create scripts so that windows users can download and install PredictionIO on their windows machines. > Scripts for Windows > --- > > Key: PIO-88 > URL: https://issues.apache.org/jira/browse/PIO-88 > Project: PredictionIO > Issue Type: New Feature >Reporter: Sara Asher > Labels: newbie > > Create scripts so that windows users can download and install PredictionIO on > their windows machines. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-88) Scripts for Windows
[ https://issues.apache.org/jira/browse/PIO-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-88: -- Labels: newbie (was: ) > Scripts for Windows > --- > > Key: PIO-88 > URL: https://issues.apache.org/jira/browse/PIO-88 > Project: PredictionIO > Issue Type: New Feature >Reporter: Sara Asher > Labels: newbie > > Create scripts so that windows users can download and install PredictionIO on > their windows machines. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-88) Scripts for Windows
Sara Asher created PIO-88: - Summary: Scripts for Windows Key: PIO-88 URL: https://issues.apache.org/jira/browse/PIO-88 Project: PredictionIO Issue Type: New Feature Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (PIO-87) Fix doc licensing issues
[ https://issues.apache.org/jira/browse/PIO-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025808#comment-16025808 ] Sara Asher commented on PIO-87: --- [~pferrel] Can you list out what the licensing issues are? > Fix doc licensing issues > > > Key: PIO-87 > URL: https://issues.apache.org/jira/browse/PIO-87 > Project: PredictionIO > Issue Type: Bug >Reporter: Sara Asher > Fix For: 0.12.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-87) Fix doc licensing issues
Sara Asher created PIO-87: - Summary: Fix doc licensing issues Key: PIO-87 URL: https://issues.apache.org/jira/browse/PIO-87 Project: PredictionIO Issue Type: Bug Reporter: Sara Asher Fix For: 0.12.0-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-86) Maintain a working docker container
Sara Asher created PIO-86: - Summary: Maintain a working docker container Key: PIO-86 URL: https://issues.apache.org/jira/browse/PIO-86 Project: PredictionIO Issue Type: Wish Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-85) Add a method to make engine IDs settable and used with all workflow phases
Sara Asher created PIO-85: - Summary: Add a method to make engine IDs settable and used with all workflow phases Key: PIO-85 URL: https://issues.apache.org/jira/browse/PIO-85 Project: PredictionIO Issue Type: Improvement Components: Core Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-84) Move to Elasticsearch 5.x as the default, when using ES, deprecating older versions.
Sara Asher created PIO-84: - Summary: Move to Elasticsearch 5.x as the default, when using ES, deprecating older versions. Key: PIO-84 URL: https://issues.apache.org/jira/browse/PIO-84 Project: PredictionIO Issue Type: Improvement Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-81) Remove pio build and replace with sbt targets for templates.
[ https://issues.apache.org/jira/browse/PIO-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-81: -- Issue Type: Improvement (was: Bug) > Remove pio build and replace with sbt targets for templates. > > > Key: PIO-81 > URL: https://issues.apache.org/jira/browse/PIO-81 > Project: PredictionIO > Issue Type: Improvement > Components: Build >Reporter: Sara Asher > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PIO-82) Improve debugging experience in IntelliJ/Eclipse when developing templates
[ https://issues.apache.org/jira/browse/PIO-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sara Asher updated PIO-82: -- Issue Type: Improvement (was: Bug) > Improve debugging experience in IntelliJ/Eclipse when developing templates > --- > > Key: PIO-82 > URL: https://issues.apache.org/jira/browse/PIO-82 > Project: PredictionIO > Issue Type: Improvement >Reporter: Sara Asher > > From Pat: Make debugging templates with IntelliJ or Eclipse much easier. This > may be helped by #1 above but perhaps also by doing refactoring of the CLI > layers. This is the single worst roadblock to getting templates developed. I > figured it out (with Donald) and documented it once upon a time but things > you do, like changing the build.sbt or other things, can wipe out the config > that was working, causing you to start over. I suspect the somewhat odd > support for ES1 and ES5 may have complicated this. This IMO would help more > than writing templates in Java! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-83) Move to Spark 2.x and Scala 2.11 as the default env with deprecating (not deprecated) support for previous tools chain.
Sara Asher created PIO-83: - Summary: Move to Spark 2.x and Scala 2.11 as the default env with deprecating (not deprecated) support for previous tools chain. Key: PIO-83 URL: https://issues.apache.org/jira/browse/PIO-83 Project: PredictionIO Issue Type: Improvement Components: Core Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-82) Improve debugging experience in IntelliJ/Eclipse when developing templates
Sara Asher created PIO-82: - Summary: Improve debugging experience in IntelliJ/Eclipse when developing templates Key: PIO-82 URL: https://issues.apache.org/jira/browse/PIO-82 Project: PredictionIO Issue Type: Bug Reporter: Sara Asher >From Pat: Make debugging templates with IntelliJ or Eclipse much easier. This >may be helped by #1 above but perhaps also by doing refactoring of the CLI >layers. This is the single worst roadblock to getting templates developed. I >figured it out (with Donald) and documented it once upon a time but things you >do, like changing the build.sbt or other things, can wipe out the config that >was working, causing you to start over. I suspect the somewhat odd support for >ES1 and ES5 may have complicated this. This IMO would help more than writing >templates in Java! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PIO-81) Remove pio build and replace with sbt targets for templates.
Sara Asher created PIO-81: - Summary: Remove pio build and replace with sbt targets for templates. Key: PIO-81 URL: https://issues.apache.org/jira/browse/PIO-81 Project: PredictionIO Issue Type: Bug Components: Build Reporter: Sara Asher -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: JIRA and release process for PredictionIO
Hi everyone, It looks like everyone is content with the JIRA/release process doc. If I don't hear from anyone else in the next day or so, I will assume it's good and will add the details to the public documentation for PredictionIO. Thanks, Sara On Thu, May 18, 2017 at 1:30 PM, Donald Szeto wrote: > +1. Thanks Sara! > > On Thu, May 18, 2017 at 8:48 AM Sara Asher wrote: > > > Hi everyone, > > > > Thank you for allowing me to join the PredictionIO team! > > > > To start with, I would like to document a process for using JIRA and to > > suggest a standard release cadence for PredictionIO. > > > > I've worked with Donald to come up with the following: > > > > https://docs.google.com/document/d/1nQpENncXZq72KeI3WMe_ > > X8Xz8HKkYO2QC12GD3ZKP9g/edit?usp=sharing > > > > Please comment and give suggestions! When you are all content, I will > add > > this to our public documentation. > > > > Thanks, > > Sara > > >
[GitHub] incubator-predictionio issue #384: Correct typo : addiiton -> addition
Github user takezoe commented on the issue: https://github.com/apache/incubator-predictionio/pull/384 @puchka Thanks. I merged this request to `livedoc` branch, so it will be applied the web site soon. This pull request will be closed automatically when this fix is merged to `develop` branch later. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-predictionio pull request #384: Correct typo : addiiton -> additio...
GitHub user puchka opened a pull request: https://github.com/apache/incubator-predictionio/pull/384 Correct typo : addiiton -> addition You can merge this pull request into a Git repository by running: $ git pull https://github.com/puchka/incubator-predictionio livedoc-typo-correct-addition Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-predictionio/pull/384.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #384 commit a79c26808de67b6b03457cb552abceae9627c5ea Author: Marius A. Rabenarivo Date: 2017-05-25T06:11:10Z Correct typo : addiiton -> addition --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (PIO-80) Docs on Custom Backend Support are Wrong
James Ward created PIO-80: - Summary: Docs on Custom Backend Support are Wrong Key: PIO-80 URL: https://issues.apache.org/jira/browse/PIO-80 Project: PredictionIO Issue Type: Bug Components: Documentation Reporter: James Ward Priority: Minor The docs for Using Another Data Store - https://predictionio.incubator.apache.org/system/anotherdatastore/ - indicate that the custom fat jar should go into a "plugins" dir. But the contents of that dir don't actually go into the CLASSPATH. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
