You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by Zulfiqar Ali <zu...@gmail.com> on 2015/03/04 09:27:17 UTC
Falcon bi-weekly collaboration meeting - 4th Mar 2015 - MOM
Thanks all for joining the sync up meeting. MOM are following:
1. Revamp Falcon documentation - Ajay to raise JIRA. Srikanth will comment
his thoughts around doc structure and various required sections. Ajay will
work over this item.
2. Configure Jenkins job or cron job to keep SVN doc and Git doc in sync.
3. Peeyush will fix Jenkins build (distributed) failing due to JAVA_HOME
setting. JAVA_HOME should point to v1.7.
4. Trigger 'commit' build in Jenkins for 'PATCH AVAILABLE' JIRAs. Reviewers
need to cancel the status (change status from 'PATCH AVAILABLE' to
something else) if they want patch to be updated. This is to avoid running
'commit' build for incomplete/incorrect patches. Only committers have
access to build boxes. JIRA is currently assigned to Srikanth. If he can't
get to this, he will un-assign it.
5. Lineage should support bootstrapping FALCON-1059
<https://issues.apache.org/jira/browse/FALCON-1059> and handle transactions
properly FALCON-1060 <https://issues.apache.org/jira/browse/FALCON-1060>
6. Prism should have its own graph store for entity lineage, and delegate
instance lineage requests to Server.
7. Auth support in Falcon - All metadata mutation should be subjected to
auth rules. Is FaclonAuthorizationFilter getting triggered ?
8. Balu will document Falcon 0.5 to 0.6 migration steps. Reference: FALCON-1063
<https://issues.apache.org/jira/browse/FALCON-1063>
JIRAs with status 'PATCH_AVAILABLE' we discussed are:
9. FALCON-1031 <https://issues.apache.org/jira/browse/FALCON-1031> -
Pallavi to followup with Shaik.
10. FALCON-1024 <https://issues.apache.org/jira/browse/FALCON-1024> - Ajay
will review it.
11. FALCON-929 <https://issues.apache.org/jira/browse/FALCON-929> - Pallavi
will review it.
12. FALCON-910 <https://issues.apache.org/jira/browse/FALCON-910> - Karan
will sync up with Srikanth.
Thanks
Zulfi
RE: Falcon bi-weekly collaboration meeting - 4th Mar 2015 - MOM
Posted by Srikanth Sundarrajan <sr...@hotmail.com>.
* https://issues.apache.org/jira/browse/FALCON-273 tracks pre-commit builds. This is pending for a long time, will try and get this moving.
* https://issues.apache.org/jira/browse/FALCON-1065 - For keeping docs upto date.
* https://issues.apache.org/jira/browse/FALCON-428 - Has some notes on federation of lineage api from prism to servers. However this should be limited to instance based lineage. For entity dependency prism is the sole authority and system of record.
Regards
Srikanth Sundarrajan
> Date: Wed, 4 Mar 2015 13:57:17 +0530
> Subject: Falcon bi-weekly collaboration meeting - 4th Mar 2015 - MOM
> From: zulfiali@gmail.com
> To: dev@falcon.apache.org
>
> Thanks all for joining the sync up meeting. MOM are following:
>
> 1. Revamp Falcon documentation - Ajay to raise JIRA. Srikanth will comment
> his thoughts around doc structure and various required sections. Ajay will
> work over this item.
>
> 2. Configure Jenkins job or cron job to keep SVN doc and Git doc in sync.
>
> 3. Peeyush will fix Jenkins build (distributed) failing due to JAVA_HOME
> setting. JAVA_HOME should point to v1.7.
>
> 4. Trigger 'commit' build in Jenkins for 'PATCH AVAILABLE' JIRAs. Reviewers
> need to cancel the status (change status from 'PATCH AVAILABLE' to
> something else) if they want patch to be updated. This is to avoid running
> 'commit' build for incomplete/incorrect patches. Only committers have
> access to build boxes. JIRA is currently assigned to Srikanth. If he can't
> get to this, he will un-assign it.
>
> 5. Lineage should support bootstrapping FALCON-1059
> <https://issues.apache.org/jira/browse/FALCON-1059> and handle transactions
> properly FALCON-1060 <https://issues.apache.org/jira/browse/FALCON-1060>
>
> 6. Prism should have its own graph store for entity lineage, and delegate
> instance lineage requests to Server.
>
> 7. Auth support in Falcon - All metadata mutation should be subjected to
> auth rules. Is FaclonAuthorizationFilter getting triggered ?
>
> 8. Balu will document Falcon 0.5 to 0.6 migration steps. Reference: FALCON-1063
> <https://issues.apache.org/jira/browse/FALCON-1063>
>
> JIRAs with status 'PATCH_AVAILABLE' we discussed are:
>
> 9. FALCON-1031 <https://issues.apache.org/jira/browse/FALCON-1031> -
> Pallavi to followup with Shaik.
> 10. FALCON-1024 <https://issues.apache.org/jira/browse/FALCON-1024> - Ajay
> will review it.
> 11. FALCON-929 <https://issues.apache.org/jira/browse/FALCON-929> - Pallavi
> will review it.
> 12. FALCON-910 <https://issues.apache.org/jira/browse/FALCON-910> - Karan
> will sync up with Srikanth.
>
> Thanks
> Zulfi