p生态圈。 1.2 Hadoop 发展历史（了解） Hadoop发展历史 1）Hadoop创始人Doug Cutting，为了实现与Google类似的全文搜索功能，他在Lucene框架基础上进行优 化升级，查询引擎和索引引擎。 Hadoop创始人Doug Cutting 2）2001年年底Lucene成为Apache基金会的一个子项目。 3）对于海量数据的场景，Lucene框 –前端 –python 人工智能资料下载，可百度访问：尚硅谷官网 Hadoop发展历史 6）2003-2004年，Google公开了部分GFS和MapReduce思想的细节，以此为基础Doug Cutting等人用 了2年业余时间实现了DFS和MapReduce机制，使Nutch性能飙升。 7）2005 年Hadoop 作为 Lucene的子项目 Nutch的一部分正式引入Apache基金会。 月份，Map-Reduce和Nutch Distributed File System （NDFS）分别被纳入到 Hadoop 项目 中，Hadoop就此正式诞生，标志着大数据时代来临。 9）名字来源于Doug Cutting儿子的玩具大象 Hadoop的logo 1.3 Hadoop 三大发行版本（了解） Hadoop 三大发行版本：Apache、Cloudera、Hortonworks。 Apache

Nutch 的 Doug Cutting 主導開發 Lucene 是個全文檢索的程式 庫，Nutch 是個搜尋引擎 依循著 Google 2003/2004 年發表的論文來開發 2006 年從 Nutch 獨立出來， 稱為 Hadoop Hadoop 是 Doug 兒子黃色大象 玩偶的名稱 2008-01 Apache 的 Top- Level Project 2009-09 Doug Cutting 加入 JDBC 與 MapReduce 進行彼此的資料轉換 38 / 74 不論是人數或顏色，實在都很難分辨。 Hadoop 戰隊 39 / 74 Hadoop Distribution Doug Cutting 先生在 2011 年 Hadoop World 的 Keynote 說： The similarity between Hadoop and Linux kernel, and the

Thanks also to the efforts of: ● Mitch Connors ● Nathan Mittler ● Francois Pesce ● Lin Sun ● Doug Reid ● Sven Mawson ● Jason Wang ● Martin Ostrowski ● Steve Dake #IstioCon Thank you! Istio

development process to increase user needs. KPIPs should be used for significant user-facing or cross-cutting changes, not minor incremental improvements. When in doubt, if a committer thinks a change needs The release branch pattern is branch-{MAJOR_VERSION}.{MINOR_VERSION}, e.g. branch-1.3. After cutting release branch, don’t forget bump version in master branch. Build a release candidate 1. Set environment

development process to increase user needs. KPIPs should be used for significant user-facing or cross-cutting changes, not minor incremental improvements. When in doubt, if a committer thinks a change needs The release branch pattern is branch-{MAJOR_VERSION}.{MINOR_VERSION}, e.g. branch-1.3. After cutting release branch, don’t forget bump version in master branch. Build a release candidate 1. Set environment

development process to increase user needs. KPIPs should be used for significant user-facing or cross-cutting changes, not minor incremental improvements. When in doubt, if a committer thinks a change needs The release branch pattern is branch-{MAJOR_VERSION}.{MINOR_VERSION}, e.g. branch-1.3. After cutting release branch, don’t forget bump version in master branch. 4.5. Build a release candidate 1. Set

development process to increase user needs. KPIPs should be used for significant user-facing or cross-cutting changes, not minor incremental improvements. When in doubt, if a committer thinks a change needs The release branch pattern is branch-{MAJOR_VERSION}.{MINOR_VERSION}, e.g. branch-1.3. After cutting release branch, don’t forget bump version in master branch. 4.5. Build a release candidate 1. Set

development process to increase user needs. KPIPs should be used for significant user-facing or cross-cutting changes, not minor incremental improvements. When in doubt, if a committer thinks a change needs The release branch pattern is branch-{MAJOR_VERSION}.{MINOR_VERSION}, e.g. branch-1.3. After cutting release branch, don’t forget bump version in master branch. Build a release candidate 1. Set environment

development process to increase user needs. KPIPs should be used for significant user-facing or cross-cutting changes, not minor incremental improvements. When in doubt, if a committer thinks a change needs The release branch pattern is branch-{MAJOR_VERSION}.{MINOR_VERSION}, e.g. branch-1.3. After cutting release branch, don’t forget bump version in master branch. Build a release candidate 1. Set environment

development process to increase user needs. KPIPs should be used for significant user-facing or cross-cutting changes, not minor incremental improvements. When in doubt, if a committer thinks a change needs The release branch pattern is branch-{MAJOR_VERSION}.{MINOR_VERSION}, e.g. branch-1.3. After cutting release branch, don’t forget bump version in master branch. 4.5. Build a release candidate 1. Set