This page provides a roadmap for the .NET SDK For Hadoop. This document reflect potential direction, and will evolve over time as we get more feedback.

The Road to 1.0

Over the next 3-6 months, we want to move towards a 1.0 release of the SDK. The SDK will add components over time, and we will make it clear the quality level for a given component's release.  We plan to release every two weeks as we iterate on these components.

Components

Initially, this SDK contains an API for writing [Map/Reduce] jobs, as well as submitting them. The next components which will be delivered are:

  • LINQ to Hive
    • Tooling to generate types
    • Integration with Templeton/WebHCat
    • Experiment enabling UDF's
    • Support for Partions and advanced Hive DDL
    • LINQPad integration
  • Job Submission API
  • WebHDFS Client

 

Quality Levels

With each release, for each component, we want to make it clear the level of maturity for that component.  We want to do this to ship regularly, as well as set appropriate expectations.

  • Release (RTM)
    • Quality level/ testing: 100% complete unit tests, 100% complete integration and scenario testing, all quality gates met
    • Feature complete: 100%
    • Commitment to ship as released in the future: n/a
    • Support:  formal support via CSS
    • Breaking changes in future: minimal breaking changes (as required for security issues, data corruption)
  • Preview (CTP)
    • Quality level/ testing: 100% complete unit tests, ~50% complete integration and scenario testing, some quality gates met
    • Feature complete: 80-90%
    • Commitment to ship as released in the future: strong commitment
    • Support:  unsupported go live license, forums, direct support with TAP and internal customers.   Minimal qfes (may fix significant issues + dcrs in next rev) for important customers (TAP, internal)
    • Breaking changes in future: minimal breaking changes
  • Experimental
    • Quality level/ testing: 80% complete unit tests, light integration testing
    • Feature complete: 30 – 70%, scripted scenarios and samples work
    • Commitment to ship as released in the future: low commitment
    • Support:  forums, direct support with TAP and internal customers.   No qfes (may fix significant issues + dcrs in next rev)
    • Breaking changes in future: no contract.  Likely significant breaking changes going forward.
  • Internal/ Demo
    • Quality level/ testing: 20% complete unit tests
    • Feature complete: 10 -30%, scripted scenarios and samples work
    • Commitment to ship as released in the future: no commitment
    • Support:  none
    • Breaking changes in future: no contract.  Significant breaking changes going forward.

Last edited Nov 19, 2012 at 5:56 PM by mwinkle, version 6

Comments

No comments yet.