Event Store 6.0.0 Preview 3

Merge pull request #236 from EventStore/cluster-terminology

Rename Master to Leader

Event Store 3.9.0 UI

Event Store UI

• (#135) - Display the reason when there is an error creating a competing consumer
• (#134) - Show errors thrown when a chunk has been scavenged

Event Store 3.8.0 UI

Event Store UI

• (#128) - Add an option to track and delete the streams a projection emits to.
• (#130) - Show failures and errors for scavenges on the admin and scavenge screens.

Event Store 3.7.0 UI

Event Store UI

• (#127) - Add a note to indicate to the user that there might have been an issue writing the status of the scavenge to disk if the scavenge status does not appear to be updating.

Event Store 3.6.0 UI

Event Store UI

• (#118) - Changed the wording on scavenge screen from Running to Not Finished
• (#119) - The partition method expects the isJson as the second parameter. (See kurrent-io/KurrentDB#846)
• (#121) - Fixed "projections not enabled" error when refreshing the projections page.
• (#122) - Allow non-admin users to log in to the admin UI.

Event Store UI 3.5.0

Event Store UI v3.5.0 includes fixes for the previous v3.4.0 UI. They are listed below along with the relevant pull requests or issues where relevant

Event Store UI

• (#111) - Show TCP stats in the UI
• (#113) - Shows stats about replicas in a cluster
• (#114) - Adding seconds on the Created Date and Timestamp columns
• (#116) - Redirect the user if they try to access projections when they're disabled
• (#108) - Show scavenge status in the UI

Event Store UI 3.4.0

Event Store UI v3.4.0 includes fixes for the previous v3.3.1 UI. They are listed below along with the relevant pull requests or issues where relevant

Event Store UI

• (#106) - Update the stored/cookie credentials when necessary.

Event Store UI 3.3.1

Event Store UI v3.3.1 includes fixes for the previous v3.3.0 UI. They are listed below along with the relevant pull requests or issues where relevant

Event Store UI

• (f177ebc) - When creating a persistent subscription and it fails, show the reason for the failure.
• (3383d8c) -
  Include a view to show the status of the cluster.

Event Store UI 3.3.0

Event Store UI v3.3.0 includes fixes for the previous v3.2.0 UI. They are listed below along with the relevant pull requests or issues where relevant

Event Store UI

• (#77) - Disable update button on updating of the query.
• (#76) -
  Improvements to the debugging experience which includes
  • Disables and Resets the query ready for the debugging session to commence.
  • Read the information (state, stats, etc) from the projection before enabling (this gets rid of some projections (transient) that run until completion and no longer produce a position which the UI uses to read events
  • When there are no further events for the projection to process, set running status as true (i.e. the projection is not being paused for debugging)
  • When we update the projection, we disable it to stop it from updating and running to completion, we will enable it when the debugging session has reloaded
• (#86) - Fix grammatical error in failure msg
• (#79) - Create Persistent Subscriptions from the UI
• (#84) - Retain the user's query where an update causes compilation to fail
• (#91) - Inform the user when the state query didn't return an ES-Position and possible causes.
• (#83) - Show a possible causes of 404 on Query updating
• (#82) - Show a message to the user telling them that they should press the update button for their "changed" query to take effect
• (#90) - Credentials will now be stored against the domain and port. This addresses an issue where previously only the domain was used and the UI will use the same credentials on the same domain (but different ports). The result is that the user will only see data from the first logged in instance

Event Store UI 3.2.0

Event Store UI v3.2.0 includes fixes for the previous v3.1.0 UI. They are listed below along with the relevant issue numbers.

Event Store UI

• Add Competing Consumers menu items.
  b2a6532
• Change Competing Consumers status indicator in addition to rounding by 2 decimal places.
  56f5e7e
  If the subscription is behind by more than 0 messages and the average number of items/s processed is greater than 0, the status indicator is green.
  If the subscription is behind by more than 0 messages and the average number of items/s is 0, then the status indicator is red.
  If the subscription is idle, the status indicator is green.