[GitHub] incubator-predictionio issue #274: pio train error

GitHub user birdspring opened an issue: https://github.com/apache/incubator-predictionio/issues/274 pio train error "pio build" is successfully executed on my machine. But when I tried "pio train", an error occurred to me, the log is as follows: [INFO] [Engine] Extracting

Re: 0.10.0 release

Thanks for the clarification. I could have phrased that better too. Not meant to sound abrasive. On Tue, Aug 16, 2016 at 3:53 PM, Pat Ferrel wrote: > I don’t expect you to know where Simon is, I was just seeing if anyone on > the list knew, some are relatives and friends

Re: 0.10.0 release

As I explained on the INFRA JIRA Pat I'm quite clear what was granted and if it's not already in an Apache repo it was not granted by that SGA. Sure, Simon would be a reasonable place to start for a new SGA discussion. I have no idea what he's up to, I'm not his keeper. On Tue, Aug 16, 2016 at

Re: 0.10.0 release

I see that Pat filed INFRA-12441 ( https://issues.apache.org/jira/browse/INFRA-12441) which I read asks to import code from GitHub repositories under the old PIO organization not yet granted to the ASF. This presents you with a great opportunity to learn how software grants work. (smile) Even

Re: 0.10.0 release

I agree with removing all reference to pio-build sbt plugin from engine templates. We will not need the "version tracking" and the pioVersion settings in engine template's sbt once we start tagging our officially tested templates. On Tue, Aug 16, 2016 at 2:17 PM, Pat Ferrel

Re: 0.10.0 release

Go to https://issues.apache.org/jira/ and log in. Find the read 'Create' button. There's a drop down menu immediately to the right of it. Open that menu, then click on 'New Git Repository'. The original request was here: https://issues.apache.org/jira/browse/INFRA-12112 The second request for

Re: 0.10.0 release

I've changed the namespace for all repos marked "official" except for Universal Recommender and is running integration tests on them. Also, I believe the sbt plugin for pio-build needs to be updated. On Tue, Aug 16, 2016 at 12:50 PM, Pat Ferrel wrote: > Let me know if

[jira] [Created] (PIO-24) move templates to apache git repos

Pat Ferrel created PIO-24: - Summary: 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:

[GitHub] incubator-predictionio issue #273: PIO-20 Merge ActionML fork

Github user pferrel commented on the issue: https://github.com/apache/incubator-predictionio/pull/273 inactive, this has been merged with develop --- 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

[GitHub] incubator-predictionio pull request #273: PIO-20 Merge ActionML fork

Github user pferrel closed the pull request at: https://github.com/apache/incubator-predictionio/pull/273 --- 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

[GitHub] incubator-predictionio pull request #269: ActionML Master merge PR, discussi...

Github user pferrel closed the pull request at: https://github.com/apache/incubator-predictionio/pull/269 --- 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

[jira] [Commented] (PIO-20) Merge ActionML fork

[ https://issues.apache.org/jira/browse/PIO-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423201#comment-15423201 ] ASF GitHub Bot commented on PIO-20: --- Github user pferrel commented on the issue:

[jira] [Commented] (PIO-20) Merge ActionML fork

[ https://issues.apache.org/jira/browse/PIO-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423202#comment-15423202 ] ASF GitHub Bot commented on PIO-20: --- Github user pferrel closed the pull request at:

Re: 0.10.0 release

BTW the infra Jiras to get repos created is probably critical path so can someone coach me on what to ask for? On Aug 16, 2016, at 11:16 AM, Pat Ferrel wrote: I’ve been talking abut this issue since before we were in the incubator, probably because I maintain one of

Re: 0.10.0 release

I’ve been talking abut this issue since before we were in the incubator, probably because I maintain one of the most used templates. My vote is to get it right, then release otherwise we create a lot of headaches and ramifications that may never get solved. So in the do-ocracy I’ll volunteer

Re: Why is the MaxNumberOfEventsPerBatchRequest is 50?

Thanks Donald, will create a JIRA ticket and keep you posted, Mani Teja On Tue, Aug 16, 2016 at 10:41 PM, Donald Szeto wrote: > Hi Mani Teja, > > I believe this value is just a measure to avoid sending in huge batches in > a single request. I highly encourage you to make

Re: Spark update

Hi Marcin, This is really great work, and I agree that we should cross build against different versions of Spark. If we have a cross building infrastructure set up, we can be more flexible and adapt to different versions of external dependencies as well, such as different versions of Hadoop and

Re: Why is the MaxNumberOfEventsPerBatchRequest is 50?

Hi Mani Teja, I believe this value is just a measure to avoid sending in huge batches in a single request. I highly encourage you to make this configurable so that other users do not need to rebuild from source should they find this value too small for their use case. Please feel free to file a

Why is the MaxNumberOfEventsPerBatchRequest is 50?

Can anyone please help me out with this? If i change this value to a higher number, will this work? What is the reason behind fixing this value. Thanks, Mani Teja