Hiļ¼all We have finished vote about livy-client and will submit codebase soon, This is Livy Client Codebase Intellectural Property Clearance Status in attached file.
Best Regards Zhefeng Wang
Livy Client Codebase Intellectual Property (IP) Clearance Status Description Livy-Client is a kind of higher-layer spark client, User execute shell script with Livy-Client like using script provided by spark client. Livy-Client parse all parameters in script and filled into rest template and submit to livy server. The difference between Livy-Client and spark client is Livy-Client submit spark job to livy server and user don't need to install a spark client in local machine. Livy-Client is designed to replace existing spark client which may have different version and spread on each user machine, user can submit spark job by script as before, and these spark jobs are monitored and managed by livy. In order to minimize user's perception about change spark client to Livy-Client, Livy-Client adapt most of all parameters in spark client scripts and livy rest api, and because of using livy to submit jobs, user can fully enjoy Livy's security verification, session management, multi-tenancy and other functions. Project info This codebase will be donated into incubator livy This codebase can be merged as a sub project of livy Officer or member managing donation: jassywang1...@gmail.com Completed tasks are shown by the completion date (YYYY-MM-dd). Identify the codebase 2019-07-09 If applicable, make sure that any associated name does not already exist and is not already trademarked for an existing software product. We are preparing codebase now, and codebase will be submitted soon. MD5 or SHA1 sum for donated software: (Note versioned software used to calculate sum in parentheses). Copyright 2019-07-09 Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. 2019-07-09 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. Identify name recorded for software grant: the name of the grant as recorded in the foundation/officers area, in either grants.txt or cclas.txt, so that the grant can be easily identified. If recorded in the grants.txt document, use the "for" or title. If recorded in the cclas.txt document, use the company name (field 2 without submitter name) and the "form on file" name (field 4, without any people's names). Verify distribution rights Corporations and individuals holding existing distribution rights: For individuals, use the name as recorded on the committers page 2019-07-09 Check that all active committers have a signed CLA on record. 2019-07-09 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is required to authorize their contributions under their individual CLA. 2019-07-09 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. 2019-07-09 Check and make sure that all items depended upon by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms. Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License. Organizational acceptance of responsibility for the project Related VOTEs: https://issues.apache.org/jira/browse/LIVY-596 [VOTE]: Support Livy client for script submitting Solution
