You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,29 @@
1
1
# Changelog
2
2
3
+
## 0.7.0 - 2023-04-28
4
+
- Added initial support for live data with `LiveBlocking` and `LiveThreaded` clients
5
+
- Added support for statistics schema
6
+
- Added `SystemMsg` and `ErrorMsg` records for use in live data
7
+
- Added `strike_price`, `strike_price_currency`, and `instrument_class` to `InstrumentDefMsg`
8
+
- Renamed `BatchJob.cost` to `cost_usd` and value now expressed as US dollars
9
+
- Added `FixedPx` helper class for formatting fixed prices
10
+
- Added configurable log receiver `ILogReceiver`
11
+
- Added `instrument_class`, `strike_price`, and `strike_price_currency` to definition schema
12
+
- Added additional `condition` variants for `DatasetConditionDetail` (degraded, pending, missing)
13
+
- Added additional member `last_modified_date` to `DatasetConditionDetail` Added `has_mixed_schema`, `has_mixed_stype_in`, and `ts_out` to `Metadata` to support live data
14
+
- Removed `related` and `related_security_id` from `InstrumentDefMsg`
15
+
- Renamed `SType::ProductId` to `SType::InstrumentId` and `SType::Native` to `SType::RawSymbol`
16
+
- Renamed `RecordHeader::product_id` to `instrument_id`
17
+
- Renamed `InstrumentDefMsg::symbol` to `raw_symbol`
18
+
- Renamed `SymbolMapping::native_symbol` to `raw_symbol`
19
+
- Deprecated `SType::Smart` to split into `SType::Parent` and `SType::Continuous`
20
+
- Changed `expiration` and `action` type to `UnixNanos`
21
+
- Changed some fields to enums in `InstrumentDefMsg`
22
+
- Added optional `compression` parameter to `BatchSubmitJob`
23
+
- Fixed parsing of `BatchSubmitJob` response
24
+
- Fixed invalid read in `DbnDecoder`
25
+
- Fixed memory leak in `TryCreateDir`
26
+
3
27
## 0.6.1 - 2023-03-28
4
28
- Fixed Zstd decoding of files with multiple frames
5
29
- Removed usage of unreliable `std::ifstream::readsome`
To run this program, replace `YOUR_API_KEY` with an actual API key.
11
+
The minimum C++ standard is C++11 and the minimum CMake version is 3.14.
36
12
37
-
Additional example standalone executables are provided in the [examples](./examples) directory.
38
-
These examples can be compiled by enabling the cmake option `DATABENTO_ENABLE_EXAMPLES` with `-DDATABENTO_ENABLE_EXAMPLES=1` during the configure step.
39
-
40
-
### Documentation
41
-
42
-
More detailed examples and the full API documentation can be found on the [Databento doc site](https://docs.databento.com/getting-started).
13
+
### Integration
43
14
44
-
## Integration
15
+
The easiest way to use our library is by embedding it with [CMake FetchContent](https://cmake.org/cmake/help/v3.11/module/FetchContent.html).
16
+
Your `CMakeLists.txt` should look something like the following:
45
17
46
-
databento-cpp can be integrated into C++ projects in a couple of different ways.
47
-
48
-
### Embedded
49
-
50
-
The easiest way to integrate databento-cpp into your project is using CMake's [FetchContent](https://cmake.org/cmake/help/latest/module/FetchContent.html).
To run this program, replace `$YOUR_API_KEY` with an actual API key.
155
142
156
-
To setup OpenSSL and zstd, run the following:
157
-
```sh
158
-
brew install openssl zstd
159
-
# Add it to the PATH so cmake can find it
160
-
export"$PATH:$HOMEBREW_PREFIX/opt/openssl/bin"
161
-
```
143
+
Additional example standalone executables are provided in the [examples](./examples) directory.
144
+
These examples can be compiled by enabling the cmake option `DATABENTO_ENABLE_EXAMPLES` with `-DDATABENTO_ENABLE_EXAMPLES=1` during the configure step.
162
145
163
-
For linting on macOS, the best way to install clang-tidy and clang-format is to install all of LLVM
164
-
and symlink the binaries to some place in your `PATH`.
You can find more detailed examples and the full API documentation on the [Databento doc site](https://docs.databento.com/getting-started?historical=cpp&live=cpp).
0 commit comments