GCHQDev404

Results 38 issues of GCHQDev404

# Related Issue - Resolve #2357

Some tests could be pulled out IT. Some tests could be in ITS class using a different "publicAccessPredefinedFederatedStore" with zero graphs?

federated-store

Following the bug raised and fixed in gh-1992. Should the views been validated at all? Can the view validation be removed completely and opChains simply return null if the view...

enhancement
question

Braking change. change isAddingUser and similar reference to isCreatingUser

p:normal
tech-def
federated-store

FederatedStore-FederatedAccess: Why are Read Write Predicates Strings and not AccessPredicate objects? This requires deserialisation on every usage of FederatedAccess on graphs, This seems wasteful.

enhancement
p:low
federated-store

Append `class` to all `HashCodeBuilders` in Gaffer for the below issue to minimise hash collisions. ``` @Test void name() { Foo foo = new Foo(); Bar bar = new Bar();...

enhancement

Recursion of the opChain is no longer required and adds complexity. doOperation -> Unprocessed Logic -> ResolvedLogic -> ToHandlers OR ToProxy

federated-store
proxy-store

Previously there have been bug in `FederatedStore` regarding options map being shared between operations/stores example see gh-2445. This was fixed with a deep clone of `JSONSerialisation` which is a little...

enhancement
p:low
tech-def
possible-bug
federated-store

When querying `GetAllNamedOperations` the field `InputType` is created and populated into the `NamedOperationDetail` object during the logic of `GetAllNamedOperationsHandler`. Why is this not created and added to the named operation...

enhancement
question
p:low
possible-bug
named-operation

The Accumulo specific code in FederatedGraphStorage fixes mismatch in tables and graph name. 1. Does a similar problem effect other stores? 2. Does this code belong somewhere else Possible Likely...

p:low
tech-def
federated-store