[PDB-4270] Support a new "configure expiration" command Created: 2019/02/25 Updated: 2019/03/26 Resolved: 2019/03/20
|Fix Version/s:||PDB 6.3.0|
|Reporter:||Austin Blatt||Assignee:||Rob Browning|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Release Notes:||New Feature|
|Release Notes Summary:||An experimental "configure expiration" command has been added. It currently allows specifying that factsets should (the longstanding default) or should not be candidates for expiration. See the documentation for further information and some caveats, and note that as an experimental command, it might be altered or removed in a future release.|
|QA Risk Assessment:||Needs Assessment|
For now we'll only support setting factset expiration to true or false.
DB/command names are not set in stone.
Add an endpoint (and a feature flag?) that accepts and stores a command that looks like.
|Comment by Rob Browning [ 2019/03/21 ]|
Heston Hoffman Yeah, should have mentioned that – if you look at the "git log -p" and search (typically via '/') for
|Comment by Heston Hoffman [ 2019/03/21 ]|
Thanks Rob Browning, I've linked to the doc from the release note