Adding Search as a first-class citizen to Hadoop

<!--HTML--><p align="justify">Apache Hadoop is enabling organizations to collect larger, more varied data - but after it&#39;s collected how will it be found? Your users expect to be able to search for information using simple text based queries -- regardless of data location, size, and complexity. How do they quickly find information that&#39;s just been created, or been stored for months or even years? <a href="http://www.cloudera.com" target="_blank">Cloudera</a> Search Senior Software Engineer <a href="http://www.linkedin.com/pub/wolfgang-hoschek/1/621/77a" target="_blank">Wolfgang Hoschek </a>will present a solution to this problem; what architecture is necessary to search HDFS and HBase? How was Apache Solr, Lucene, Flume and MapReduce integrated to allow for Near Real Time and Batch indexing of data? What are the solved problems and what&#39;s still to come? Join us for an exciting discussion on this new technology.</p> <h4>About the speaker</h4> <p align="justify">Wolfgang Hoschek is a Software Engineer at Cloudera working on the Hadoop Platform and Cloudera Search team. He is a committer on the Apache Flume and Apache Lucene/Solr projects, a committer on the Kite project, a committer on the Lily HBase Indexer project, and the lead developer on Morphlines. He is a former CERN fellow and former Computer Scientist at Lawrence Berkeley Laboratory, and former Senior Software Engineer at Skytide. He has 15+ years of experience in large-scale distributed systems, data intensive computing and real time analytics. He received his Ph.D in Computer Science from the Technical University of Vienna, Austria.</p>