-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace getTrait usages with Operation #2581
Comments
I think this is should happen after #2791 because the traits is often based on values in the schema. |
The related |
* gh-2890 cache service single static instance bug removal. * Revert "gh-2890 cache service single static instance bug removal." This reverts commit 59b23ab. * gh-2890 cache service single static instance bug removal. K.I.S.S * gh-2890 cache service single static instance bug removal. K.I.S.S Tests * gh-2890 cache service. delete backwards compatibility 1.12 * gh-2890 cache service single static instance bug removal. K.I.S.S Tests * gh-2890 cache service single static instance bug removal. spotbugs * gh-2890 cache service static instance bug. proof test. * checkstyle * gh-2581 getTraits to use operation, tidy up. --------- Co-authored-by: GCHQDev404 <GCHQDev404@users.noreply.github.com>
There are some problems with the GetTrait operation returning different results to the method. See PR #2901 for details. |
Problems with the PR have been resolved by using the operation option to not get current traits - ready for PR to be reviewed. |
* Remove getTraits from Store * Remove getTraits from Graph * Remove getTraits from Map Store * Remove getTraits from Accumulo Store * Remove getTraits from Core Rest * Remove getTraits from Proxy Store * Fix to ensure user info doesn't get lost Federated Store needs the user * Remove getTraits from Federated Store * Remove getTraits from Spring Rest * Revert disabling IT for Federated Store Fails due to QUERY_AGGREGATION Trait not being reported as a Trait of this store * Change uses of GetTraits operation to get all supported traits By default this operation gets the currently supported traits. It needs to get all supported instead as that is what the method used to do. * Improve description of endpoint for Spring * Simplify test in FederatedStoreUtilTest * Fix for handling null User in OperationChainValidator * Update Copyright * Restore getTraits method for Map Store internal use Using the static field directly would work, except this is overriden in some child classes which requires a getter to be used. * Enable handler for GetTraits in proxy store Previously this was unused as the handler was not added. Handler works the same as getTrait method did, removing visibility trait from returned traits. Also set other unused handler to null. * Copyright corrections * Fix test to include newly supported Operation in Proxy Store * ProxyStoreBasicIT should get all supported traits and not current This has no effect on the test currently but makes it clear what should be tested * Revert superseded change identified in PR comment
…-2580-fix-federatedstore-checks-for-DYNAMIC_SCHEMA
Closed by #2901 |
#2552 removed deprecated code, however, the
getTraits
function is still used (although deprecated).Similar to #2573, the function version of
getTraits
should be replaced by executing theGetTraits
Operation.This, however, cannot be done as part of alpha 1 and has to be done later. This is because it is reliant upon #2580 which needs to be done with the major FederatedStore changes.
The text was updated successfully, but these errors were encountered: