I tried the same passcode as before: 802 596 9285
On 4/5/16, 10:40 PM, "Ying Zheng" wrote:
>Dear all,
>
>I tried four times to join our bi-weekly call tonight, but it always gave
>me ³invalid passcode². Do we have any limit on the number of people who
>can join the call? Any idea why this happen
Dear all,
I tried four times to join our bi-weekly call tonight, but it always gave
me ³invalid passcode². Do we have any limit on the number of people who
can join the call? Any idea why this happened? Thank you!
Cheers,
Ying
On 3/21/16, 11:57 AM, "Balu Vellanki Bala"
wrote:
>Hi Team,
>
>I f
[
https://issues.apache.org/jira/browse/FALCON-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227674#comment-15227674
]
Venkatesan Ramachandran commented on FALCON-1889:
-
Thanks [~ajayyadava].
[
https://issues.apache.org/jira/browse/FALCON-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227649#comment-15227649
]
Ajay Yadava commented on FALCON-1889:
-
This may be helpful for you to look at - FALCO
Venkatesan Ramachandran created FALCON-1889:
---
Summary: Falcon JMS created too many topics - one per process/feed
Key: FALCON-1889
URL: https://issues.apache.org/jira/browse/FALCON-1889
Projec
[
https://issues.apache.org/jira/browse/FALCON-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkatesan Ramachandran reassigned FALCON-1888:
---
Assignee: Venkatesan Ramachandran
> Falcon JMS Notification details
Venkatesan Ramachandran created FALCON-1888:
---
Summary: Falcon JMS Notification details and documentation
Key: FALCON-1888
URL: https://issues.apache.org/jira/browse/FALCON-1888
Project: Falco
Hello everyone,
For quite some time we have been discussing to make a 1.0 release and have
had several discussions in developer sync up around it. Taking this to next
step, I propose next release line(after 0.10) of Apache Falcon to be 1.0
*Item 1 - Scope and Timelines*
Some of the items that ar
[
https://issues.apache.org/jira/browse/FALCON-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226635#comment-15226635
]
ASF GitHub Bot commented on FALCON-1882:
GitHub user PraveenAdlakha opened a pull
GitHub user PraveenAdlakha opened a pull request:
https://github.com/apache/falcon/pull/87
FALCON-1882 Instance status api not working via prism
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PraveenAdlakha/falcon 1882
Alternat
Pragya Mittal created FALCON-1887:
-
Summary: Process schedule fails when entity contains optional
dataSet
Key: FALCON-1887
URL: https://issues.apache.org/jira/browse/FALCON-1887
Project: Falcon
[
https://issues.apache.org/jira/browse/FALCON-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-1887:
--
Description:
Process schedule fails in dry run when entity contains optional dataSet.
Process
[
https://issues.apache.org/jira/browse/FALCON-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-1887:
--
Description:
Process schedule fails in dry run when entity contains optional dataSet.
Process
GitHub user ajayyadava opened a pull request:
https://github.com/apache/falcon/pull/86
FALCON-1886 Feed sla monitoring does not work across restarts.
Removed redundant fields.
Added unit tests.
You can merge this pull request into a Git repository by running:
$ git pull htt
[
https://issues.apache.org/jira/browse/FALCON-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226233#comment-15226233
]
ASF GitHub Bot commented on FALCON-1886:
GitHub user ajayyadava opened a pull req
[
https://issues.apache.org/jira/browse/FALCON-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha reassigned FALCON-1885:
---
Assignee: Praveen Adlakha
> SLA monitoring API throws ResultNotFoundException
> ---
Ajay Yadava created FALCON-1886:
---
Summary: Feed sla monitoring does not work across restarts
Key: FALCON-1886
URL: https://issues.apache.org/jira/browse/FALCON-1886
Project: Falcon
Issue Type:
Pragya Mittal created FALCON-1885:
-
Summary: SLA monitoring API throws ResultNotFoundException
Key: FALCON-1885
URL: https://issues.apache.org/jira/browse/FALCON-1885
Project: Falcon
Issue T
[
https://issues.apache.org/jira/browse/FALCON-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-1884:
--
Description:
Status api result is :
{noformat}
dataqa@lda01:/mnt/falcon/server/bin$ ./falcon in
Pragya Mittal created FALCON-1884:
-
Summary: Status api not honouring numResults in case of native
scheduler
Key: FALCON-1884
URL: https://issues.apache.org/jira/browse/FALCON-1884
Project: Falcon
[
https://issues.apache.org/jira/browse/FALCON-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225799#comment-15225799
]
Pragya Mittal commented on FALCON-1882:
---
This happens for all the apis having lifec
21 matches
Mail list logo
