[jira] [Updated] (PIO-27) Check release artifacts for licenses and the LICENSE.txt file

[ https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated PIO-27: -- Issue Type: Task (was: Bug) > Check release artifacts for licenses and the LICENSE.txt f

[jira] [Commented] (PIO-27) Check release artifacts for licenses and the LICENSE.txt file

[ https://issues.apache.org/jira/browse/PIO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429484#comment-15429484 ] Pat Ferrel commented on PIO-27: --- It looks like some work has gone into these but they hav

[jira] [Created] (PIO-27) Check release artifacts for licenses and the LICENSE.txt file

Pat Ferrel created PIO-27: - Summary: Check release artifacts for licenses and the LICENSE.txt file Key: PIO-27 URL: https://issues.apache.org/jira/browse/PIO-27 Project: PredictionIO Issue Type

Re: Apache PIO v0.10.0 release

jars have been accounted for and the License and Notice files are included in the appropriate project release artifacts. On Sat, Aug 20, 2016 at 2:00 PM, Pat Ferrel wrote: > What do people think remains for release? > > 1) template donation and mods. Chan Lee has done work on this but

Apache PIO v0.10.0 release

What do people think remains for release? 1) template donation and mods. Chan Lee has done work on this but we can’t review until the donation and repos are set up. 2) install.sh. There are some suggestions on how to deal with the one-line install here: https://issues.apache.org/jira/browse/PIO-

[jira] [Updated] (PIO-18) Documentation for setting up the project for developers

[ https://issues.apache.org/jira/browse/PIO-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated PIO-18: -- Priority: Minor (was: Major) > Documentation for setting up the project for develop

[jira] [Commented] (PIO-18) Documentation for setting up the project for developers

[ https://issues.apache.org/jira/browse/PIO-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429466#comment-15429466 ] Pat Ferrel commented on PIO-18: --- I think this works, but you need to create the correct c

[jira] [Resolved] (PIO-13) Update Gemnasium dependency status

[ https://issues.apache.org/jira/browse/PIO-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel resolved PIO-13. --- Resolution: Fixed seems fixed on the develop branch > Update Gemnasium dependency sta

[jira] [Commented] (PIO-13) Update Gemnasium dependency status

[ https://issues.apache.org/jira/browse/PIO-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429462#comment-15429462 ] Pat Ferrel commented on PIO-13: --- This seems to have been fixed. [~xusen] I'll clos

[jira] [Commented] (PIO-11) Current version (v0.9.8) of python sdk requires python3

[ https://issues.apache.org/jira/browse/PIO-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429460#comment-15429460 ] Pat Ferrel commented on PIO-11: --- Can you describe this. Did you mean python3? I use it

[jira] [Updated] (PIO-9) Clean up examples under examples/

[ https://issues.apache.org/jira/browse/PIO-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated PIO-9: - Priority: Minor (was: Major) > Clean up examples under examp

Re: templates

will do what I can to drive it. There will be no problem with third party (or templates of any provenance) calling PIO code in an org.apache namespace going forward, of course. I also don't think this is particularly new ground for Apache. > On Aug 20, 2016, at 9:54 AM, Pat Ferrel wrote:

Re: templates

that depends on templates in this uncertain condition I'm > afraid I would need to vote -1 (binding) until this is resolved or we have > clarification it's ok. > >> On Aug 19, 2016, at 10:09 PM, Pat Ferrel wrote: >> >> No misunderstanding—so far at least :-)

Re: templates

mported, I think you should wait. If you > post a release of PIO that depends on templates in this uncertain condition > I'm afraid I would need to vote -1 (binding) until this is resolved or we > have clarification it's ok. > >> On Aug 19, 2016, at 10:09 PM, Pat Ferrel

Old Google Group and lost users

The old Google Group for PIO was fairly active but it seems all of those users have vanished. I suggest that this is bad for the project as well as the user base. One possible solution is to retract the no-posting rule and forward all posts to the user@ list address. Then questions will get answ

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

[ https://issues.apache.org/jira/browse/PIO-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429432#comment-15429432 ] Pat Ferrel commented on PIO-24: --- [~chanlee514] are you willing to put your modified templ

Re: templates

e and update minimum PIO version as 0.10. I will leave out the tests for now. But personally, I think it would be better if we wait for the legal grant issue to be resolved, so that it is clearer how template code should be managed. On Thu, Aug 18, 2016 at 1:13 PM, Pat Ferrel mailto:p...@oc

templates

I think we are not waiting for the official template donation to release PIO, can you point me to the templates you have working? I’ll make sure they get added to the new gallery. We can push them to Apache once the grant is done. Thanks for the help.

[jira] [Commented] (PIO-22) Install.sh issues

[ https://issues.apache.org/jira/browse/PIO-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426974#comment-15426974 ] Pat Ferrel commented on PIO-22: --- What if we rename this script "source-install.sh&

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

[ https://issues.apache.org/jira/browse/PIO-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel resolved PIO-20. --- Resolution: Done > Merge ActionML fork > --- > >

Re: 0.10.0 release

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 3:36 PM, Pat Ferrel wrote: > AFAIK Salesforce owns the code and Simon must have filled out the original > PIO grant, which may cover all the

Re: 0.10.0 release

ht 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 site was here: https://issues.apache. > org/jira/browse/INFRA-12180 > > >

Re: 0.10.0 release

al 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 mailto:p...@occamsmachete.com>> wrote: Let me know if anything is missing: https://issues.apache.org/jira/

Re: 0.10.0 release

Let me know if anything is missing: https://issues.apache.org/jira/browse/PIO-24 On Aug 16, 2016, at 12:26 PM, Pat Ferrel wrote: +1 > On Aug 16, 2016, at 11:35 AM, Donald Szeto <mailto:don...@apache.org>> wrote: > > 1) I’ll volunteer to take a couple templates and put

[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

Re: 0.10.0 release

+1 > On Aug 16, 2016, at 11:35 AM, Donald Szeto wrote: > > 1) I’ll volunteer to take a couple templates and put them in their own repos > if we can get some created. > Sure. I believe Chan might have some converted repos as well. > > 2) do we have a gallery page yet? we had a good proposal,

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 the most used templates

Re: 0.10.0 release

engine one repo, but I think otherwise it would be hard for customized engines to merge upstream official changes. On Mon, Aug 15, 2016 at 3:05 PM, Pat Ferrel wrote: > Possible but we have template in examples/ for testing and that’s ok imo. > If we think separate repos is the way to go w

Re: asking why error

Internally all pio recommenders get user history from the EventServer before consulting the model to get recommendations, This seems to have timed out for that query. I don’t think this is a PIO parameter but would check to see if the EventServer is setup to respond quickly. If not you will get

Re: Cannot install prediction.io

This ActionML.com instructions are for installing our fork. Get this from our repo as instructed. This will get you going until we get everything merged. Installing PIO from Apache is not quite ready for users yet since we don’t have an Apache release. We’re working to fix the install and docs a

Re: 0.10.0 release

arcin mentioned, we can expand tests to keep track of performance changes as well. Also, I think we should consider merging the current examples/ directory with the templates/ directory. Thanks, Chan On Sun, Aug 14, 2016 at 8:30 AM, Pat Ferrel mailto:p...@occamsmachete.com>> wrote: Importa

[jira] [Created] (PIO-23) links in release.md need to be removed or updated

Pat Ferrel created PIO-23: - Summary: links in release.md need to be removed or updated Key: PIO-23 URL: https://issues.apache.org/jira/browse/PIO-23 Project: PredictionIO Issue Type: Task

[jira] [Created] (PIO-22) Install.sh issues

Pat Ferrel created PIO-22: - Summary: Install.sh issues Key: PIO-22 URL: https://issues.apache.org/jira/browse/PIO-22 Project: PredictionIO Issue Type: Task Affects Versions: 0.10.0

[jira] [Commented] (PIO-21) Checks in Travis build not the same as local build

[ https://issues.apache.org/jira/browse/PIO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420548#comment-15420548 ] Pat Ferrel commented on PIO-21: --- I think it is my local problem, can't run the integra

[jira] [Resolved] (PIO-21) Checks in Travis build not the same as local build

[ https://issues.apache.org/jira/browse/PIO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel resolved PIO-21. --- Resolution: Invalid > Checks in Travis build not the same as local bu

Re: 0.10.0 release

n Aug 14, 2016, at 8:30 AM, Pat Ferrel wrote: > > Important things unresolved for release: > > 1) What to do with Apache templates—my suggestion is separate repos for the 3 > reasons below. > 2) We need a Gallery page listing at least a couple converted tested > templates—c

0.10.0 release

ther than releasing with templates in a templates/ directory. Anything else? How are people feeling about release? On Aug 12, 2016, at 10:18 AM, Pat Ferrel wrote: Independent of Apache I’d suggest each template have their own git repo as they do now. Is this practically possible in ASF (ano

Re: PIO-20 problems

trying to rebuild the image from scratch? Is there somewhere in the integration test documentation that can be improved? On Sat, Aug 13, 2016 at 12:31 PM, Alex Merritt mailto:emergentor...@apache.org>> wrote: Resolved, passing in Travis now. On Fri, Aug 12, 2016 at 3:04 PM, Pat Ferrel ma

Re: PIO-20 problems

Alex, can you look at these unit test failures on the PR, they seem to be in JDBCPEvents https://travis-ci.org/apache/incubator-predictionio/builds/151905196 On Aug 12, 2016, at 1:18 PM, Pat Ferrel wrote: Can't install unittest with pip or pip3 even though the rest of the prerequi

Re: PIO-20 problems

ching distribution found for unittest Tried forcing the version to 0.0 but again no luck Ideas? In the meantime waiting for Travis to do it—sigh On Aug 11, 2016, at 2:31 PM, Pat Ferrel wrote: With the keystore my template-based integration test passes and I’ve put the keystore back in. The diffs on P

Re: transition from "official" PredictionIO templates to Apache

d > Marcin just submitted ( > https://github.com/apache/incubator-predictionio/pull/267 > <https://github.com/apache/incubator-predictionio/pull/267>). That way we > can > make commitment to included templates be part of every committer's effort. > Just my 2c. > > On

Re: PIO-20 problems

maybe this was not clear enough. If you > have any additional questions or run into issues executing the tests, > please let me know. > > Thanks, > Chan > > On Thu, Aug 11, 2016 at 6:07 AM, Pat Ferrel wrote: > >> I’m always disinclined to commit code that has not be

PIO-20 problems

I’m always disinclined to commit code that has not been tested. However many things in the current state of the develop branch seem broken or at least too big to address in a single commit. 1) Style test fail in Travis that are not runnable or at least have not been documented for local build.

[jira] [Commented] (PIO-1) Make SSL and authKey param authentication optional

[ https://issues.apache.org/jira/browse/PIO-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416212#comment-15416212 ] Pat Ferrel commented on PIO-1: -- Templates still fail on `pio deploy` when SSL is not config

[jira] [Created] (PIO-21) Checks in Travis build not the same as local build

Pat Ferrel created PIO-21: - Summary: Checks in Travis build not the same as local build Key: PIO-21 URL: https://issues.apache.org/jira/browse/PIO-21 Project: PredictionIO Issue Type: Bug

Re: Trying to merge PR

) ... 18 more On Aug 10, 2016, at 1:31 PM, Pat Ferrel wrote: I’m trying to build a template against the aml/apache merged pio. Obviously there are a few template code changes needed so I started with a completely clean EventServer meaning HBase and Elasticsearch were completely wiped and

Re: Trying to merge PR

) ... 18 more On Aug 10, 2016, at 1:31 PM, Pat Ferrel wrote: I’m trying to build a template against the aml/apache merged pio. Obviously there are a few template code changes needed so I started with a completely clean EventServer meaning HBase and Elasticsearch were completely wiped and

Re: Trying to merge PR

On Aug 10, 2016, at 1:32 PM, Pat Ferrel wrote: I’m trying to build a template against the aml/apache merged pio. Obviously there are a few template code changes needed so I started with a completely clean EventServer meaning HBase and Elasticsearch were completely wiped and restarted. I

Trying to merge PR

I’m trying to build a template against the aml/apache merged pio. Obviously there are a few template code changes needed so I started with a completely clean EventServer meaning HBase and Elasticsearch were completely wiped and restarted. I deleted manifest.json and was able to build, and train.

Trying to merge PR

I’m trying to build a template against the aml/apache merged pio. Obviously there are a few template code changes needed so I started with a completely clean EventServer meaning HBase and Elasticsearch were completely wiped and restarted. I deleted manifest.json and was able to build, and train.

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

Pat Ferrel created PIO-20: - Summary: Merge ActionML fork Key: PIO-20 URL: https://issues.apache.org/jira/browse/PIO-20 Project: PredictionIO Issue Type: Bug Reporter: Pat Ferrel

Re: transition from "official" PredictionIO templates to Apache

too as long as the committer is willing to support the template. As far as the Salesforce templates marked official, I’d hope that most would be donated. According to the proposed rules all we need is a PR for each. And again a big thanks to Salesforce! On Aug 4, 2016, at 2:55 PM, Pat Ferrel

[jira] [Commented] (MAHOUT-1853) Improvements to CCO (Correlated Cross-Occurrence)

[ https://issues.apache.org/jira/browse/MAHOUT-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409595#comment-15409595 ] Pat Ferrel commented on MAHOUT-1853: Great, that's what I wanted to hear.

Re: transition from "official" PredictionIO templates to Apache

Actually this is mostly a fine idea but I think the bigger question is how do we treat templates in general. IMO the maintaining author can decide to contribute them or not and the committers can decide to accept or not. For example in the case of the UR I may decide to support and maintain it

[jira] [Commented] (MAHOUT-1853) Improvements to CCO (Correlated Cross-Occurrence)

[ https://issues.apache.org/jira/browse/MAHOUT-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408326#comment-15408326 ] Pat Ferrel commented on MAHOUT-1853: If t-digest is more tolerant of "n

[jira] [Commented] (MAHOUT-1853) Improvements to CCO (Correlated Cross-Occurrence)

[ https://issues.apache.org/jira/browse/MAHOUT-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408256#comment-15408256 ] Pat Ferrel commented on MAHOUT-1853: is rootLLR normally distributed (the posi

[jira] [Comment Edited] (MAHOUT-1853) Improvements to CCO (Correlated Cross-Occurrence)

[ https://issues.apache.org/jira/browse/MAHOUT-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391126#comment-15391126 ] Pat Ferrel edited comment on MAHOUT-1853 at 8/4/16 4:1

[jira] [Updated] (MAHOUT-1853) Improvements to CCO (Correlated Cross-Occurrence)

[ https://issues.apache.org/jira/browse/MAHOUT-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1853: --- Sprint: Jan/Feb-2016 > Improvements to CCO (Correlated Cross-Occurre

Re: IntelliJ IDEA

; I’m using IntelliJ too so maybe we can figure it out and update the how-to. On Aug 3, 2016, at 11:07 PM, Hyukjin Kwon wrote: I am using intelliJ. Would there be any potential problem with this? 2016-07-30 4:01 GMT+09:00 Pat Ferrel mailto:p...@occamsmachete.com>>: Is anyone using a d

Re: Inquery about the stroage and other file formats on HDFS and local FS.

This would work for some templates but not all. The Events as a collection need to support PEvents and LEvents APIs and files would make those type of queries rather difficult. I believe the current philosophy for PIO is that to include something in the core it would need to support all template

Re: Cleanup app

Thanks Alex. My pet feature :-) On Aug 2, 2016, at 2:42 PM, Alex Merritt wrote: It does look like we do need a new delete method there. I will take a look at this today. On Tue, Aug 2, 2016 at 8:47 AM, Pat Ferrel wrote: > I’m trying to merge the AML fork and looked deeper into the clea

Re: Support mailing list policy

On Aug 2, 2016, at 8:03 AM, Pat Ferrel wrote: > > Since Simon made the old pio Google Group read only there have been no posts > to the Apache user list and afaik no subscribes. This is not a good thing. Indeed. An Apache branded release with PR from the foundation (we can coordina

Cleanup app

I’m trying to merge the AML fork and looked deeper into the cleanup app, which we turned into a optional feature of any Datasource. In the cleanup app example it uses an RDD.collect, which is not scalable. It seems that PEvents does not really support delete so you have to get the `eventsToDelet

Re: [Proposal] Integration tests

Oops I see the code now. If it were a PR the discussion would be copied to the dev@ address On Jul 30, 2016, at 10:45 AM, Pat Ferrel wrote: Very nice step and I agree with the no-Scala approach. From my experience answering questions on several forums for users over the last year. PIO

Re: [Proposal] Integration tests

d template(s). Maybe the directory structure can be > something like this? > root/ > test/ >integration/ > EventserverSuite.scala > AppSuite.scala > SimilarProductTemplateSuite.scala > > seed/ > json data for testing eventserver >json data for testi

IntelliJ IDEA

Is anyone using a debugger with PredictionIO itself (not template code)?

Re: [Proposal] The new template gallery

guidelines on how to submit new templates. Introduced changes <https://github.com/apache/incubator-predictionio/compare/develop...Ziemin:template-gallery> śr., 20.07.2016 o 16:56 użytkownik Pat Ferrel napisał: > If we used the same mechanisms supported in the site generator it would > simp

Re: First release

. Hoping to get Jenkins running soon. How about Aug 8 as our first release? Due to all these package name changes, I'd also like to suggest to start a new minor version. How about 0.10.0? Regards, Donald On Sat, Jul 23, 2016 at 7:45 AM, Pat Ferrel wrote: > I’d like to propose a first minimum

[jira] [Commented] (PIO-10) bin/install.sh doesn't work due to bad links

[ https://issues.apache.org/jira/browse/PIO-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391175#comment-15391175 ] Pat Ferrel commented on PIO-10: --- Also the fork merge from AML will capture the need

[jira] [Commented] (MAHOUT-1853) Improvements to CCO (Correlated Cross-Occurrence)

[ https://issues.apache.org/jira/browse/MAHOUT-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391126#comment-15391126 ] Pat Ferrel commented on MAHOUT-1853: To reword this issue... The CCO analysis

First release

I’d like to propose a first minimum release from Apache to include: 1) SSL optional (I think @alex has already merged this PR) 2) Heal ActionML fork 3) change to Apache class naming and include Apache license notices in all code 4) live doc site 5) Apache classes published to the maven/sbt univers

Re: [Proposal] Integration tests

+1 for integration tests. We have one for the UR that tests PIO too and can be a starter. It is probably possible to create one that is template independent that only tests the EventServer or some null template. https://github.com/actionml/template-scala-parallel-universal-recommendation/blob/m

Fwd: pio app new hangs, can't create app

Begin forwarded message: From: Nilay Khatri Subject: Re: pio app new hangs, can't create app Date: July 20, 2016 at 1:58:56 PM PDT To: predictionio-user Facing same issue with Digitalocean 4GB Ram PredictionIO-0.9.6. Unable to create a new app. It just hangs. On Friday, June 24, 2016 at 9:

Re: [Proposal] The new template gallery

If we used the same mechanisms supported in the site generator it would simplify support. Yaml is fine but isn’t middleman in ruby?Maybe you don’t need a separate Python script. On Jul 20, 2016, at 9:50 AM, Donald Szeto wrote: Hey Marcin, I think this looks great for now! I think it is fine t

Doc site

Some of us were talking on Slack and came up with the plan to have a docs/ directory in the main repo that will hold a Jekyll docs site. Whenever this is committed to, Jenkins will push this to a separate repo to which gitpubsub is connected. This will allow easier user PRs to docs and still mai

Re: Services are completely down

ttp://incubator.apache.org/guides/sites.html> says we should have a site at http://predictionio.incubator.apache.org/ Has a Jira been filed for infra to create this? If not I can do this. On Jul 17, 2016, at 6:22 PM, Pat Ferrel wrote: Not sure how to subscribe to the Google group from

Re: Services are completely down

/pirk.incubator.apache.org/ >> <http://pirk.incubator.apache.org/> and the mailing lists are active. >> >> As far as Apache goes I think they have fulfilled all requests that were >> asked of them, the onus is now on PMC to jump start the project. >> >&

Re: Services are completely down

TLDR; rely on ActionML.com because we offer commercial support for PredictionIO and use https://groups.google.com/forum/#!forum/actionml-user but watch for developments on the Apache mailing list here: user@predictionio.incubator.apache.o

Re: HBase warn on startup

.mbox/%3ccaep_jwbf1kghmsl272hymtodskts68tp6b3lh2ecsq-nwe9...@mail.gmail.com%3E <http://mail-archives.apache.org/mod_mbox/hbase-user/201505.mbox/%3ccaep_jwbf1kghmsl272hymtodskts68tp6b3lh2ecsq-nwe9...@mail.gmail.com%3E> On Wed, Jul 13, 2016 at 2:42 PM, Pat Ferrel mailto:p...@occamsmachete.com>> wrote: I saw a question Tom asked

HBase warn on startup

I saw a question Tom asked about this error when doing `pio status` Was there every an answer for what causes it? [INFO] [Storage$] Verifying Event Data Backend (Source: HBASE)... [INFO] [Storage$] Test writing to Event Store (App Id 0)... [WARN] [MetaReader] No serialized HRegionInfo in keyvalu

[jira] [Commented] (PIO-6) Create doc site

[ https://issues.apache.org/jira/browse/PIO-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373925#comment-15373925 ] Pat Ferrel commented on PIO-6: -- Is there an infra Jira to follow on this? Who is in charg

[jira] [Commented] (PIO-6) Create doc site

[ https://issues.apache.org/jira/browse/PIO-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373924#comment-15373924 ] Pat Ferrel commented on PIO-6: -- Is there an infra Jira to follow on this? Who is in charg

[jira] [Created] (PIO-7) document use of SSL

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

Re: All Github PR closed

work on. > On Jul 4, 2016, at 10:35 AM, Pat Ferrel wrote: > > Creating a Jira for a PR is all well and fine but using pathces + Jira is a > pretty archaic and cumbersome way to handle PRs. If we simply reopen the PR > against the mirror github repo then all conversations there

Re: All Github PR closed

(as patch) to the new > PIO JIRA instance? > > There is some discussion about allowing GH Issues as a blessed resource for > development workflow, but we are not there yet where there is guidance for > podlings (or even TLPs). > > On Thu, Jun 30, 2016 at 4:04 PM, Pat Ferrel

[jira] [Created] (PIO-6) Create doc site

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

[jira] [Commented] (PIO-1) Make SSL and authKey param authentication optional

[ https://issues.apache.org/jira/browse/PIO-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361573#comment-15361573 ] Pat Ferrel commented on PIO-1: -- Can we make sure SSL is opt-in? meaning non-SSL unless other

Re: The future of PIO

-snapshop, a months long WIP with relatively ambitious goals. If this discussion is seen as constructive by the PMC it should probably be moved to dev@ to get user’s input. On Jul 2, 2016, at 6:06 PM, Suneel Marthi mailto:suneel.mar...@gmail.com>> wrote: On Sat, Jul 2, 2016 at 8:58 P

Re: Development Model

+1 (in general) The only issue will be when we have more than one release to support. For instance Elasticsearch 2.x forces an upgrade on all users and so may not be a good idea to add to our songle release branch, which is the master. This or other cases will eventually require us to have more

Re: predictionio.NotCreatedError: Exception happened: [Errno 111] Connection refused for request POST /

disabled until our Apache migration is complete and stable. On Fri, Jul 1, 2016 at 10:01 AM, Pat Ferrel mailto:p...@occamsmachete.com>> wrote: Shouldn’t all exceptions (well the vast majority) be caught in that code so no error would cause a failure of a build? On Jul 1, 2016, at 9:55 AM, Pat

Re: predictionio.NotCreatedError: Exception happened: [Errno 111] Connection refused for request POST /

disabled until our Apache migration is complete and stable. On Fri, Jul 1, 2016 at 10:01 AM, Pat Ferrel mailto:p...@occamsmachete.com>> wrote: Shouldn’t all exceptions (well the vast majority) be caught in that code so no error would cause a failure of a build? On Jul 1, 2016, at 9:55 AM, Pat

Re: predictionio.NotCreatedError: Exception happened: [Errno 111] Connection refused for request POST /

Shouldn’t all exceptions (well the vast majority) be caught in that code so no error would cause a failure of a build? On Jul 1, 2016, at 9:55 AM, Pat Ferrel wrote: io.prediction.workflow.UpgradeCheckRunner.run(WorkflowUtils.scala:400) Seems to be looking for "

Re: predictionio.NotCreatedError: Exception happened: [Errno 111] Connection refused for request POST /

Shouldn’t all exceptions (well the vast majority) be caught in that code so no error would cause a failure of a build? On Jul 1, 2016, at 9:55 AM, Pat Ferrel wrote: io.prediction.workflow.UpgradeCheckRunner.run(WorkflowUtils.scala:400) Seems to be looking for "

Fwd: predictionio.NotCreatedError: Exception happened: [Errno 111] Connection refused for request POST /

ertPathBuilder.build(CertPathBuilder.java:280) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:382) ... 23 more The build doesn't finish. Any help regarding the following? On Friday, July 1, 2016 at 8:29:49 PM UTC+5:30, Pat Ferrel wrote: The script is failing t

Re: All Github PR closed

PRs are closed, so it left me wondering if there is a set of conditions that were triggered when GitHub integration was turned on. On Thursday, June 30, 2016, Pat Ferrel wrote: > Maybe I missed the explanation but why are all the gitub PRs against the > PIO account closed? This is not

All Github PR closed

Maybe I missed the explanation but why are all the gitub PRs against the PIO account closed? This is not ideas, especially if some should be merged with the ASF git, because the PRs have user/branch info that can be used to hand-merge.

Re: Scaling up spark Iitem similarity on big data data sets

In addition to increasing downsampling there are some other things to note. The original OOM was caused by the use of BiMaps to store your row and column ids. These will increase with the size of the total storage needed for 2 hashmaps per id type. With only 16g you may have very little else for

subscribe

subscribe

Re: Rename tables or swap alias

ops.snapshots.clone <http://hbase.apache.org/book.html#ops.snapshots.clone> Cheers On Tue, Feb 16, 2016 at 6:35 AM, Pat Ferrel wrote: > I think I can work out the algorithm if I knew precisely what a “snapshot" > does. From my reading it seems to be a lightweight fast alias

<    5   6   7   8   9   10   11   12   13   14   >