Author: mujtaba Date: Wed Jan 21 01:10:34 2015 New Revision: 1653416 URL: http://svn.apache.org/r1653416 Log: Add who is using page
Modified: phoenix/site/publish/images/using/all.jpeg phoenix/site/publish/index.html phoenix/site/publish/news.html phoenix/site/publish/who_is_using.html phoenix/site/source/src/site/markdown/index.md phoenix/site/source/src/site/markdown/news.md phoenix/site/source/src/site/markdown/who_is_using.md Modified: phoenix/site/publish/images/using/all.jpeg URL: http://svn.apache.org/viewvc/phoenix/site/publish/images/using/all.jpeg?rev=1653416&r1=1653415&r2=1653416&view=diff ============================================================================== Binary files - no diff available. Modified: phoenix/site/publish/index.html URL: http://svn.apache.org/viewvc/phoenix/site/publish/index.html?rev=1653416&r1=1653415&r2=1653416&view=diff ============================================================================== --- phoenix/site/publish/index.html (original) +++ phoenix/site/publish/index.html Wed Jan 21 01:10:34 2015 @@ -164,7 +164,7 @@ </tr> </tbody> </table> - <p><span id="alerts" style="background-color:#ffc; text-align: center;display: block;padding:10px; border-bottom: solid 1px #cc9"> <b>News:</b> <a href="news.html">Apache Phoenix 4.2.2 released</a> (December 10, 2014) </span></p> + <p><span id="alerts" style="background-color:#ffc; text-align: center;display: block;padding:10px; border-bottom: solid 1px #cc9"> <b>News:</b> Recently added: <a href="who_is_using.html">Who is using Apache Phoenix?</a> (Jan 20, 2015) </span></p> <hr /> </div> </div> Modified: phoenix/site/publish/news.html URL: http://svn.apache.org/viewvc/phoenix/site/publish/news.html?rev=1653416&r1=1653415&r2=1653416&view=diff ============================================================================== --- phoenix/site/publish/news.html (original) +++ phoenix/site/publish/news.html Wed Jan 21 01:10:34 2015 @@ -137,8 +137,14 @@ <p></p> <div class="section"> <div class="section"> - <h3 id="Announcing_release_of_Phoenix_4.2.2_and_3.2.2_Dec._10_2014"><a class="externalLink" href="https://blogs.apache.org/phoenix/entry/announcing_phoenix_4_2_2">Announcing</a> release of Phoenix 4.2.2 and 3.2.2 (Dec. 10, 2014)</h3> - <p>For additional news and information, see our <a class="externalLink" href="https://blogs.apache.org/phoenix">blog</a> and download the latest release <a href="download.html">here</a>.</p> + <div class="section"> + <h4 id="Added_new_page:_Who_is_using_Apache_Phoenix_Jan._20_2015">Added new page: <a href="who_is_using.html">Who is using Apache Phoenix?</a> (Jan. 20, 2015)</h4> + <hr /> + </div> + <div class="section"> + <h4 id="Announcing_release_of_Phoenix_4.2.2_and_3.2.2_Dec._10_2014"><a class="externalLink" href="https://blogs.apache.org/phoenix/entry/announcing_phoenix_4_2_2">Announcing</a> release of Phoenix 4.2.2 and 3.2.2 (Dec. 10, 2014)</h4> + <p>For additional news and information, see our <a class="externalLink" href="https://blogs.apache.org/phoenix">blog</a> and download the latest release <a href="download.html">here</a>.</p> + </div> </div> </div> </div> Modified: phoenix/site/publish/who_is_using.html URL: http://svn.apache.org/viewvc/phoenix/site/publish/who_is_using.html?rev=1653416&r1=1653415&r2=1653416&view=diff ============================================================================== --- phoenix/site/publish/who_is_using.html (original) +++ phoenix/site/publish/who_is_using.html Wed Jan 21 01:10:34 2015 @@ -150,7 +150,7 @@ <td> <img src="images/using/teoco.png" alt="" /> <br /><br /> TEOCO is a leading provider of assurance and analytics solutions to communications service providers worldwide.<br /> At Teoco we use Phoenix to provide fast access to customers activity records. The system is required to manage tens of billions of records per day.<br /><br /> Phoenix allows us easy and rapid development using it's SQL interface while maintaining HBase performance and throughput. It's saves the need to handle and manage lower level operations, and allows clean and maintainable code.<br /><br /> Cahana Ori<br /> Director of Research and Development<br /> TEOCO<br /> </td> </tr> <tr class="b"> - <td> <img src="images/using/ab.png" alt="" /> <br /><br /> At Alibaba there're two main scenarios of using Pheonix:<br /><br /> 1. Large dataset with relatively small result set, say 10 thousands of records or so. We choose to use Pheonix in this kind of scenario because it's much more easier for user to use than HBase native api, meantime it supports orderby/groupby syntax<br /><br /> 2. Large dataset with large result set, it might be millions of records in the result set even after PrimaryKey filter, and often along with lots of aggregation/orderby/groupby invocation. We choose to use Pheonix in this kind of scenario because Pheonix makes it possible to do complicated query in HBase, and it supports more and more features in traditional DB like oracle, which makes it much more easier for our user to migrate there BI query onto HBase<br /><br /> Jaywong<br /> Software Engineer<br /> Alibaba<br /> </td> + <td> <img src="images/using/ab.png" alt="" /> <br /><br /> At Alibaba there're two main scenarios of using Phoenix:<br /><br /> 1. Large dataset with relatively small result set, say 10 thousands of records or so. We choose to use Phoenix in this kind of scenario because it's much more easier for user to use than HBase native api, meantime it supports orderby/groupby syntax<br /><br /> 2. Large dataset with large result set, it might be millions of records in the result set even after PrimaryKey filter, and often along with lots of aggregation/orderby/groupby invocation. We choose to use Pheonix in this kind of scenario because Pheonix makes it possible to do complicated query in HBase, and it supports more and more features in traditional DB like oracle, which makes it much more easier for our user to migrate there BI query onto HBase<br /><br /> Jaywong<br /> Software Engineer<br /> Alibaba<br /> </td> </tr> </tbody> </table> @@ -160,7 +160,7 @@ <table border="0" class="bodyTable table table-striped table-hover"> <tbody> <tr class="a"> - <td> <img src="images/using/ebay.png" alt="" /> <br /><br /> We have been exploring Phoenix since July, 2014 and have successfully achieved couple of analytics use cases with huge data set. We were able to achieve read/write performance in ms even slicing and dicing data in many dimension.<br /><br /> 1. Path or Flow analysis<br /> This use case was very specific and targeted for core mobile native apps where we were trying to find user behavior with many dimension App, Version, device , OS version, carrier etc. This was offline process where we process and aggregate daily data and load once in phoenix schema.<br /><br /> 2. Real Time analytics data trend.<br /> This is near real time aggregation of tracking data to find trend of events with multi-dimensional. It does write aggregated data to hBase + Phoenix continuously (at present 12k-15k/s records) and read for report generation at the same time.<br /><br /> Jogendar Singh<br /> Engineering Manager, Mobile Platform<br /> e bay<br /> </td> + <td> <img src="images/using/ebay.png" alt="" /> <br /><br /> We have been exploring Phoenix since July, 2014 and have successfully achieved couple of analytics use cases with huge data set. We were able to achieve read/write performance in ms even slicing and dicing data in many dimensions.<br /><br /> 1. Path or Flow analysis<br /> This use case was very specific and targeted for core mobile native apps where we were trying to find user behavior with many dimension App, Version, device , OS version, carrier etc. This was offline process where we process and aggregate daily data and load once in phoenix schema.<br /><br /> 2. Real Time analytics data trend.<br /> This is near real time aggregation of tracking data to find trend of events with multi-dimensional. It does write aggregated data to hBase + Phoenix continuously (at present 12k-15k/s records) and read for report generation at the same time.<br /><br /> Jogendar Singh<br /> Engineering Manager, Mobile Platform<br /> ebay<br /> </td> </tr> <tr class="b"> <td> <img src="images/using/ss.png" alt="" /> <br /><br /> At Sift Science we use Phoenix to power our OLAP infrastructure. This influences our machine learning feature engineering which is critical in the model training pipeline. Having a simple SQL-based interface also allows us to expose data insights outside of the engineering organization. Finally, running Phoenix on top of our existing HBase infrastructure gives us the ability to scale our ad-hoc query needs. <br /><br /> Andrey Gusev<br /> Tech Lead, Machine Learning Infrastructure<br /> Sift Science<br /> </td> Modified: phoenix/site/source/src/site/markdown/index.md URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/index.md?rev=1653416&r1=1653415&r2=1653416&view=diff ============================================================================== --- phoenix/site/source/src/site/markdown/index.md (original) +++ phoenix/site/source/src/site/markdown/index.md Wed Jan 21 01:10:34 2015 @@ -45,7 +45,7 @@ <span id="alerts" style="background-color:#ffc; text-align: center;display: block;padding:10px; border-bottom: solid 1px #cc9"> <strong>News:</strong> -<a href="news.html">Apache Phoenix 4.2.2 released</a> (December 10, 2014) +Recently added: <a href="who_is_using.html">Who is using Apache Phoenix?</a> (Jan 20, 2015) </span> <hr/> Modified: phoenix/site/source/src/site/markdown/news.md URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/news.md?rev=1653416&r1=1653415&r2=1653416&view=diff ============================================================================== --- phoenix/site/source/src/site/markdown/news.md (original) +++ phoenix/site/source/src/site/markdown/news.md Wed Jan 21 01:10:34 2015 @@ -1,5 +1,7 @@ # Apache Phoenix News <br/><hr/> -### [Announcing](https://blogs.apache.org/phoenix/entry/announcing_phoenix_4_2_2) release of Phoenix 4.2.2 and 3.2.2 (Dec. 10, 2014) +#### Added new page: [Who is using Apache Phoenix?](who_is_using.html) (Jan. 20, 2015) +<hr/> +#### [Announcing](https://blogs.apache.org/phoenix/entry/announcing_phoenix_4_2_2) release of Phoenix 4.2.2 and 3.2.2 (Dec. 10, 2014) For additional news and information, see our [blog](https://blogs.apache.org/phoenix) and download the latest release [here](download.html). Modified: phoenix/site/source/src/site/markdown/who_is_using.md URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/who_is_using.md?rev=1653416&r1=1653415&r2=1653416&view=diff ============================================================================== --- phoenix/site/source/src/site/markdown/who_is_using.md (original) +++ phoenix/site/source/src/site/markdown/who_is_using.md Wed Jan 21 01:10:34 2015 @@ -98,10 +98,10 @@ TEOCO<br/> <img src="images/using/ab.png"/> <br/><br/> -At Alibaba there're two main scenarios of using Pheonix:<br/><br/> +At Alibaba there're two main scenarios of using Phoenix:<br/><br/> 1. Large dataset with relatively small result set, say 10 thousands of -records or so. We choose to use Pheonix in this kind of scenario +records or so. We choose to use Phoenix in this kind of scenario because it's much more easier for user to use than HBase native api, meantime it supports orderby/groupby syntax<br/><br/> @@ -131,7 +131,7 @@ Alibaba<br/> We have been exploring Phoenix since July, 2014 and have successfully achieved couple of analytics use cases with huge data set. We were able to achieve read/write performance in ms even slicing and dicing -data in many dimension.<br/><br/> +data in many dimensions.<br/><br/> 1. Path or Flow analysis<br/> This use case was very specific and targeted for core mobile native