Skip to content

Commit

Permalink
Updates CHANGELOG.
Browse files Browse the repository at this point in the history
  • Loading branch information
archolewa committed Mar 1, 2017
1 parent 320bb5e commit cf67dc0
Showing 1 changed file with 9 additions and 12 deletions.
21 changes: 9 additions & 12 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,20 +37,17 @@ Current
* The previous message of `reject <url>` wasn't helpful, useful, nor very nice to users, and the message logged was
not very useful either. The message has been made nicer (`Service is unhealthy. At least 1 healthcheck is
failing`), and the log has been made better as well.
- [`RequestLog` timings support the try-with-resources block](https://github.com/yahoo/fili/pull/143)
* A block of code can now be timed by wrapping the timed block in a try-with-resources block that
starts the timer. Note: This won't work when performing timings across threads, or across
contexts. Those need to be started and stopped manually.

### Deprecated:

- [`RequestLog::stopMostRecentTimer` has been deprecated](https://github.com/yahoo/fili/pull/143)
- This method is a part of the infrastructure to support the recently
deprecated `RequestLog::switchTiming`.

- [`RequestLog::switchTiming` has been deprecated](https://github.com/yahoo/fili/pull/141)
- `RequestLog::switchTiming` is very context-dependent, and therefore brittle. In particular, adding any
additional timers inside code called by a timed block may result in the original timer not stopping
properly. All usages of `switchTiming` should be replaced with explicit calls to `RequestLog::startTiming`
and `RequestLog::stopTiming`.



### Fixed:
- Correcting error message logged when no table schema match is found
Expand Down Expand Up @@ -269,6 +266,11 @@ Changes:

### Deprecated:

- [`RequestLog::switchTiming` has been deprecated](https://github.com/yahoo/fili/pull/141)
- `RequestLog::switchTiming` is very context-dependent, and therefore brittle. In particular, adding any additional
timers inside code called by a timed block may result in the original timer not stopping properly. All usages of
`switchTiming` should be replaced with explicit calls to `RequestLog::startTiming` and `RequestLog::stopTiming`.

- [Dimension Field Tagging and Dynamic Dimension Field Serilization](https://github.com/yahoo/fili/pull/137)
* Deprecated `DimensionsServlet::getDimensionFieldListSummaryView` and `DimensionsServlet::getDimensionFieldSummaryView`
since there is no need for it anymore due to the change in serialization of `DimensionField`
Expand Down Expand Up @@ -378,11 +380,6 @@ New Capabilities & Enhancements:

### Changed:

- [`RequestLog` timings support the try-with-resources block](https://github.com/yahoo/fili/pull/143)
* A block of code can now be timed by wrapping the timed block in a try-with-resources block that
starts the timer. Note: This won't work when performing timings across threads, or across
contexts. Those need to be started and stopped manually.

- [Error messages generated during response processing include the request id.](https://github.com/yahoo/fili/pull/78)

- [`DimensionStoreKeyUtils` now supports case sensitive row and column keys](https://github.com/yahoo/fili/pull/90)
Expand Down

0 comments on commit cf67dc0

Please sign in to comment.