Apache Zeppelin (version 0.6.0) includes the ability to securely authenticate users and require logins. It uses the Apache Shiro security framework to accomplish this objective. Note: prior versions of Zeppelin did not force users to login. After launching the HDP 2.5 Tech Preview Sandbox on a virtual machine, make sure the Zeppelin service is up and running via Ambari. Next, open the Zeppelin UI either by clicking on: Services (tab) -> Zeppelin notebook (left-hand panel) -> Quick Links (tab) -> "Zeppelin UI" (button) or just by opening a browser at: http://sandbox.hortonworks.com:9995/ (or http://127.0.0.1:9995/) The Zeppelin welcome page should show in the browser, and you should notice a "Login" button in the upper right-hand corner. This will bring up a pop-up window with text entries for username and password. Enter one of the username/password pairs below (these are the defaults listed in the "shiro.ini" file located in the "conf" sub-directory of zeppelin): Username/Password pairs: admin/password1 user1/password2 user2/password3 user3/password4 If you want to change these passwords or add more users, you can use the "Credentials" tab of the Zeppelin notebook to create additional usernames. After entering the credentials, you will be logged in and the existing notebooks will display on the left-hand side of the Zeppelin screen. If you enter the wrong username or password, you will be directed back to the Welcome page. FYI: For more information about Zeppelin security, see this link: https://github.com/apache/zeppelin/blob/master/SECURITY-README.md FYI: For more detailed information about Apache Shiro configuration options, see this link: http://shiro.apache.org/configuration.html#Configuration-INISections ... View more

Just a few months ago, Apache Storm announced release 1.0 for the distribution. The bullet points below summarize the new features available. For more detailed descriptions, you can go to this link to read the full release notes: http://storm.apache.org/2016/04/12/storm100-released.html Apache Storm 1.0 Release Apache Storm 1.0 is *up to 16 times faster than previous versions, with latency reduced up to 60%.” Pacemaker – Heartbeat Server Pacemaker is an optional Storm daemon designed to process heartbeats from workers. (overcomes scaling problems of Zookeeper) Distributed Cache API Files in the distributed cache can be updated at any time from the command line, without the need to redeploy a topology. HA Nimbus Multiple instances of the Nimbus service run in a cluster and perform leader election when a Nimbus node fails Native Streaming Window API Storm has support for sliding and tumbling windows based on time duration and/or event count. Automatic Backpressure Storm now has an automatic backpressure mechanism based on configurable high/low watermarks expressed as a percentage of a task's buffer size. Resource Aware Scheduler The new resources aware scheduler (AKA "RAS Scheduler") allows users to specify the memory and CPU requirements for individual topology components Storm makes it easier to debug, with… Dynamic Log Levels Tuple Sampling and Debugging Dynamic Worker Profiling ... View more