[
https://issues.apache.org/jira/browse/EAGLE-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054116#comment-15054116
]
ASF GitHub Bot commented on EAGLE-14:
-
GitHub user yonzhang opened a pull request:
GitHub user yonzhang opened a pull request:
https://github.com/apache/incubator-eagle/pull/24
EAGLE-14: Hdfs User command re-assembler
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yonzhang/incubator-eagle master
Alternatively
[
https://issues.apache.org/jira/browse/EAGLE-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054113#comment-15054113
]
ASF GitHub Bot commented on EAGLE-14:
-
Github user yonzhang closed the pull request at:
Github user yonzhang closed the pull request at:
https://github.com/apache/incubator-eagle/pull/23
---
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 featu
ok, going forward I can develop feature on feature branch instead of
master.
But in this case, when I apply the patch in apache github, it reports
issue. https://github.com/apache/incubator-eagle/pull/23.patch
Do we have a graceful way to squash all the commits together and merge? (I
don¹t want to
Edward,
As github bot recommended as following:
===
GitHub user yonzhang opened a pull request:
https://github.com/apache/incubator-eagle/pull/23
EAGLE-14: Hdfs User command re-assembler
recreated, reviewed and to be merged
You c
Github user haoch commented on the pull request:
https://github.com/apache/incubator-eagle/pull/21#issuecomment-164105535
Rename the pull request title to "EAGLE-80: remove httpd directory" where
the ticket number is upper case.
---
If your project is set up for it, you can reply to
[
https://issues.apache.org/jira/browse/EAGLE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054002#comment-15054002
]
ASF GitHub Bot commented on EAGLE-80:
-
Github user haoch commented on the pull request:
Or can I use git diff upstream/master to get a local patch, but in that
way, this patch is not available to public?
Thanks
Edward
On 12/11/15, 17:55, "Zhang, Edward (GDI Hadoop)" wrote:
>Hi Ralph,
>
>I have some issue with merge this code change into master. I think that is
>because we have mul
Hi Ralph,
I have some issue with merge this code change into master. I think that is
because we have multiple commits for one file so it is not good to patch
to current master. (I did rebase from upstream/master also)
https://patch-diff.githubusercontent.com/raw/apache/incubator-eagle/pull/23
.pa
[
https://issues.apache.org/jira/browse/EAGLE-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053932#comment-15053932
]
ASF GitHub Bot commented on EAGLE-14:
-
GitHub user yonzhang opened a pull request:
GitHub user yonzhang opened a pull request:
https://github.com/apache/incubator-eagle/pull/23
EAGLE-14: Hdfs User command re-assembler
recreated, reviewed and to be merged
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yonzhang/i
Github user yonzhang closed the pull request at:
https://github.com/apache/incubator-eagle/pull/22
---
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 featu
[
https://issues.apache.org/jira/browse/EAGLE-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053931#comment-15053931
]
ASF GitHub Bot commented on EAGLE-14:
-
Github user yonzhang closed the pull request at:
GitHub user yonzhang opened a pull request:
https://github.com/apache/incubator-eagle/pull/22
This is re-created but reviewed already, going to be merged
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yonzhang/incubator-eagle ma
Github user yonzhang closed the pull request at:
https://github.com/apache/incubator-eagle/pull/19
---
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 featu
[
https://issues.apache.org/jira/browse/EAGLE-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053901#comment-15053901
]
ASF GitHub Bot commented on EAGLE-14:
-
Github user yonzhang closed the pull request at:
Github user yonzhang commented on the pull request:
https://github.com/apache/incubator-eagle/pull/19#issuecomment-164091345
I have fixed the license header issue, I will merge
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
[
https://issues.apache.org/jira/browse/EAGLE-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053877#comment-15053877
]
ASF GitHub Bot commented on EAGLE-14:
-
Github user yonzhang commented on the pull reques
Hi all,
Just a short question:
My system is windows 7, in Cygwin I'm using maven to build "eagle-incubator".
When it comes to "eagle-webservice", it says: "Environment Check...
npm not installed!".
The official document from npm says "installing on Cygwin: No". Does it mean I
cannot use Cygwin t
That’s cool, I will look into those new features. But does that provide
automatically snapshot and restore?
Thanks
Edward
On 12/11/15, 12:18, "P. Taylor Goetz" wrote:
>In Storm 1.0 (which we hope to release in the next month or so) adds
>distributed cache/blobstore functionality that could be l
That is a valid concern which we also are aware. It is perfect if you can
introduce some leaders of those projects for the discussions.
The good thing is that Eagle has abstracted the interface so it is
possible to change underlying streaming infrastructure (but it is not
trivial work)
But as Eag
In Storm 1.0 (which we hope to release in the next month or so) adds
distributed cache/blobstore functionality that could be leveraged to solve a
lot of the problems described in this thread. Another relevant feature is
native windowing with persistent state (currently under development).
Docum
State management of streams (including what I’d call “derived streams”) is a
hard distributed systems problem. Ideally it would be solved by the stream
provider, not by the Eagle project. I think you should talk to the various
streaming projects — Storm, Samza, Kafka, Flink — and find out whethe
Hi -
We already have a GitHub PR builder plugin installed - see
https://blogs.apache.org/infra/entry/github_pull_request_builds_now, and
https://builds.apache.org/job/cloudstack-pull-analysis/configure for an
example of how to configure to use it.
A.
On Fri, Dec 11, 2015 at 12:41 PM, Michael Wu
Amareshwarisr, thanks for informing.
On Fri, Dec 11, 2015 at 3:24 PM, amareshwarisr .
wrote:
> You can contact INFRA team for the same. Please refer
> http://www.apache.org/dev/infra-contact
>
> Thanks
>
> On Fri, Dec 11, 2015 at 12:42 PM, Michael Wu wrote:
>
> > Hi guys,
> >
> > Researched and
Hi administrators of Jenkins,
I'm using the jenkins service at builds.apache.org for incubator-eagle
project to make builds, and I'd like to integrate it with github repo to
automatically trigger builds when new pull requests comes. This requires a
plugin: "github pull request builder", be install
[
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052986#comment-15052986
]
Michael Wu commented on EAGLE-84:
-
log steps with pseudocode for reference:
> turn to the re
28 matches
Mail list logo