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

2016-08-22 Thread Pat Ferrel (JIRA)

[ 
https://issues.apache.org/jira/browse/PIO-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431865#comment-15431865
 ] 

Pat Ferrel commented on PIO-24:
---

Sorry [~chanlee514] my mistake. you don't need an ICLA until you are doing the 
push yourself. 

> move templates to apache git repos
> --
>
> Key: PIO-24
> URL: https://issues.apache.org/jira/browse/PIO-24
> Project: PredictionIO
>  Issue Type: Task
>Affects Versions: 0.10.0
>Reporter: Pat Ferrel
>Assignee: Pat Ferrel
> Fix For: 0.10.0
>
>
> https://issues.apache.org/jira/browse/INFRA-12441



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] incubator-predictionio issue #278: Website related problems

2016-08-22 Thread dszeto
Github user dszeto commented on the issue:

https://github.com/apache/incubator-predictionio/issues/278
  
@jgam04 To subscribe, please e-mail 
user-subscr...@predictionio.incubator.apache.org. No subject or content 
required in the subscription mail. ASF mailing list servers will send you a 
confirmation e-mail, which you can simply click reply and send.

Regarding the new release, we are working hard to get it out before 
September.

@moeamla We have just restored download.prediction.io. To get pre-ASF 
binaries, please use: http://download.prediction.io/PredictionIO-0.9.5.tar.gz


---
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 issue #278: Website related problems

2016-08-22 Thread dszeto
Github user dszeto commented on the issue:

https://github.com/apache/incubator-predictionio/issues/278
  
@jgam04 By the way, where is the "subscribe to user mailing list" that you 
have clicked? Was it from the bounced e-mail, or on the web site?


---
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.
---


Re: Concern for PIO user community

2016-08-22 Thread Donald Szeto
I just added huge banners to both Google groups web UI. Hope that would
help. Technically I do not think it is possible to set up forwarding. I
will sync up internally whether it's okay to turn on GGroup for the
meanwhile.

Also, last weekend the *.prediction.io domains have been migrated to
redirect to predictionio.incubator.apache.org. This should hopefully remove
all public references to Google Groups. Let's hope that would also clear up
something.

I feel that we should not support GitHub issues going forward just like all
other Apache projects are doing. For now I am manually redirecting traffic
to Apache mailing lists and JIRA.

On Mon, Aug 22, 2016 at 11:33 AM, Pat Ferrel  wrote:

> We shut off all posts to the Goggle Group for PIO. This seems to have
> resulted in loosing virtually all users. We are getting comments on github
> issues asking if the project is defunct. Notice almost no user@ emails
> when there were several a day on the Google Group—why?
>
> At the time of the last post we didn’t have instructions for how to join
> the mailing list. We now do so instructions posted to the group can now be
> updated. Also is it possible to turn on posting again and have the posts
> forwarded to u...@predictionio.incubator.apache.org ? We can turn off in
> time once people have had a reasonable amount of time to switch over.
> People need time to react, like an @Deprecated notice.
>
> Not sure who has the admin keys to the group, Donald? Simon?


[GitHub] incubator-predictionio issue #278: Website related problems

2016-08-22 Thread jgam04
Github user jgam04 commented on the issue:

https://github.com/apache/incubator-predictionio/issues/278
  
Hi, I'm also experiencing the problem of having templates.prediction.io 
re-direct immediately. Please advise.


---
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] [Commented] (PIO-25) Don't attempt to start PostgreSQL when it's not being used

2016-08-22 Thread Pat Ferrel (JIRA)

[ 
https://issues.apache.org/jira/browse/PIO-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431258#comment-15431258
 ] 

Pat Ferrel commented on PIO-25:
---

A pull request or patch is welcome.

> Don't attempt to start PostgreSQL when it's not being used
> --
>
> Key: PIO-25
> URL: https://issues.apache.org/jira/browse/PIO-25
> Project: PredictionIO
>  Issue Type: Improvement
>Reporter: David Jones
>Priority: Trivial
>
> When running: {{pio-start-all}}, even if your {{pio-env.sh}} file is setup to 
> use HBase and not PostgreSQL you'll see "postgresql: unrecognised service":
> {quote}
> Starting Elasticsearch...
> Starting HBase...
> starting master, logging to 
> /PredictionIO/vendors/hbase-1.2.2/bin/../logs/hbase--master-2898ebbfb9d1.out
> postgresql: unrecognized service
> Waiting 10 seconds for HBase to fully initialize...
> Starting PredictionIO Event Server...
> {quote}
> This is because {{pio-start-all}} simply tries to detect if PostgreSQL is 
> running, if it isn't, then it will go ahead and try to start it:
> https://github.com/apache/incubator-predictionio/blob/develop/bin/pio-start-all#L64
> What would be better is if we checked 
> {{PIO_STORAGE_REPOSITORIES_METADATA_SOURCE}}, 
> {{PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE}} and 
> {{PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE}} to see if any of those have 
> been set to {{PGSQL}}. If they have not been set to {{PGSQL}} then we don't 
> need to attempt to start PostgreSQL every time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)