graphql-engine/server/src-lib/Hasura/GraphQL/Schema/Backend.hs

204 lines
5.9 KiB
Haskell
Raw Normal View History

{- | This module defines the BackendSchema class, that a backend must implement
for its schema to be generated. From the top level of the schema down to its
leaf values, every component has a matching function in the
schema. Combinators in other modules provide a default implementation at all
layers.
Consider, for example, the following query, for a given table "author":
query {
author(where: {id: {_eq: 2}}) {
name
}
}
The chain of functions leading to a parser for this RootField will be along
the lines of:
> buildTableQueryFields
> selectTable
> tableArgs
> tableWhere
> boolExp
> comparisonExp
> columnParser
> tableSelectionSet
> fieldSelection
Several of those steps are part of the class, meaning that a backend can
customize part of this tree without having to reimplement all of it. For
instance, a backend that supports a different set ot table arguments can
choose to reimplement @tableArgs@, but can still use @tableWhere@ in its
custom implementation.
-}
module Hasura.GraphQL.Schema.Backend where
import Hasura.Prelude
import qualified Language.GraphQL.Draft.Syntax as G
import Data.Has
import Language.GraphQL.Draft.Syntax (Nullability)
import qualified Hasura.RQL.IR.Select as IR
import qualified Hasura.RQL.IR.Update as IR
import Hasura.Base.Error
import Hasura.GraphQL.Parser
import Hasura.GraphQL.Schema.Common
server: support remote relationships on SQL Server and BigQuery (#1497) Remote relationships are now supported on SQL Server and BigQuery. The major change though is the re-architecture of remote join execution logic. Prior to this PR, each backend is responsible for processing the remote relationships that are part of their AST. This is not ideal as there is nothing specific about a remote join's execution that ties it to a backend. The only backend specific part is whether or not the specification of the remote relationship is valid (i.e, we'll need to validate whether the scalars are compatible). The approach now changes to this: 1. Before delegating the AST to the backend, we traverse the AST, collect all the remote joins while modifying the AST to add necessary join fields where needed. 1. Once the remote joins are collected from the AST, the database call is made to fetch the response. The necessary data for the remote join(s) is collected from the database's response and one or more remote schema calls are constructed as necessary. 1. The remote schema calls are then executed and the data from the database and from the remote schemas is joined to produce the final response. ### Known issues 1. Ideally the traversal of the IR to collect remote joins should return an AST which does not include remote join fields. This operation can be type safe but isn't taken up as part of the PR. 1. There is a lot of code duplication between `Transport/HTTP.hs` and `Transport/Websocket.hs` which needs to be fixed ASAP. This too hasn't been taken up by this PR. 1. The type which represents the execution plan is only modified to handle our current remote joins and as such it will have to be changed to accommodate general remote joins. 1. Use of lenses would have reduced the boilerplate code to collect remote joins from the base AST. 1. The current remote join logic assumes that the join columns of a remote relationship appear with their names in the database response. This however is incorrect as they could be aliased. This can be taken up by anyone, I've left a comment in the code. ### Notes to the reviewers I think it is best reviewed commit by commit. 1. The first one is very straight forward. 1. The second one refactors the remote join execution logic but other than moving things around, it doesn't change the user facing functionality. This moves Postgres specific parts to `Backends/Postgres` module from `Execute`. Some IR related code to `Hasura.RQL.IR` module. Simplifies various type class function signatures as a backend doesn't have to handle remote joins anymore 1. The third one fixes partial case matches that for some weird reason weren't shown as warnings before this refactor 1. The fourth one generalizes the validation logic of remote relationships and implements `scalarTypeGraphQLName` function on SQL Server and BigQuery which is used by the validation logic. This enables remote relationships on BigQuery and SQL Server. https://github.com/hasura/graphql-engine-mono/pull/1497 GitOrigin-RevId: 77dd8eed326602b16e9a8496f52f46d22b795598
2021-06-11 06:26:50 +03:00
import Hasura.RQL.IR
import Hasura.RQL.Types hiding (EnumValueInfo)
-- TODO: it might make sense to add those constraints to MonadSchema directly?
type MonadBuildSchema b r m n =
( Backend b
, BackendSchema b
, MonadError QErr m
, MonadSchema n m
, MonadTableInfo r m
, MonadRole r m
, Has QueryContext r
)
class Backend b => BackendSchema (b :: BackendType) where
-- top level parsers
buildTableQueryFields
:: MonadBuildSchema b r m n
=> SourceName
-> SourceConfig b
-> TableName b
-> TableInfo b
-> G.Name
-> SelPermInfo b
-> m [FieldParser n (QueryRootField UnpreparedValue)]
buildTableRelayQueryFields
:: MonadBuildSchema b r m n
=> SourceName
-> SourceConfig b
-> TableName b
-> TableInfo b
-> G.Name
-> NESeq (ColumnInfo b)
-> SelPermInfo b
-> m [FieldParser n (QueryRootField UnpreparedValue)]
buildTableInsertMutationFields
:: MonadBuildSchema b r m n
=> SourceName
-> SourceConfig b
-> TableName b
-> TableInfo b
-> G.Name
-> InsPermInfo b
-> Maybe (SelPermInfo b)
-> Maybe (UpdPermInfo b)
-> m [FieldParser n (MutationRootField UnpreparedValue)]
buildTableUpdateMutationFields
:: MonadBuildSchema b r m n
=> SourceName
-> SourceConfig b
-> TableName b
-> TableInfo b
-> G.Name
-> UpdPermInfo b
-> Maybe (SelPermInfo b)
-> m [FieldParser n (MutationRootField UnpreparedValue)]
buildTableDeleteMutationFields
:: MonadBuildSchema b r m n
=> SourceName
-> SourceConfig b
-> TableName b
-> TableInfo b
-> G.Name
-> DelPermInfo b
-> Maybe (SelPermInfo b)
-> m [FieldParser n (MutationRootField UnpreparedValue)]
buildFunctionQueryFields
:: MonadBuildSchema b r m n
=> SourceName
-> SourceConfig b
-> FunctionName b
-> FunctionInfo b
-> TableName b
-> SelPermInfo b
-> m [FieldParser n (QueryRootField UnpreparedValue)]
buildFunctionRelayQueryFields
:: MonadBuildSchema b r m n
=> SourceName
-> SourceConfig b
-> FunctionName b
-> FunctionInfo b
-> TableName b
-> NESeq (ColumnInfo b)
-> SelPermInfo b
-> m [FieldParser n (QueryRootField UnpreparedValue)]
buildFunctionMutationFields
:: MonadBuildSchema b r m n
=> SourceName
-> SourceConfig b
-> FunctionName b
-> FunctionInfo b
-> TableName b
-> SelPermInfo b
-> m [FieldParser n (MutationRootField UnpreparedValue)]
-- table components
tableArguments
:: MonadBuildSchema b r m n
=> SourceName
-> TableInfo b
-> SelPermInfo b
-> m (InputFieldsParser n (IR.SelectArgsG b (UnpreparedValue b)))
-- backend extensions
relayExtension :: Maybe (XRelay b)
nodesAggExtension :: Maybe (XNodesAgg b)
-- individual components
columnParser
:: (MonadSchema n m, MonadError QErr m)
=> ColumnType b
-> Nullability
server: remove remnants of query plan caching (fix #1795) Query plan caching was introduced by - I believe - hasura/graphql-engine#1934 in order to reduce the query response latency. During the development of PDV in hasura/graphql-engine#4111, it was found out that the new architecture (for which query plan caching wasn't implemented) performed comparably to the pre-PDV architecture with caching. Hence, it was decided to leave query plan caching until some day in the future when it was deemed necessary. Well, we're in the future now, and there still isn't a convincing argument for query plan caching. So the time has come to remove some references to query plan caching from the codebase. For the most part, any code being removed would probably not be very well suited to the post-PDV architecture of query execution, so arguably not much is lost. Apart from simplifying the code, this PR will contribute towards making the GraphQL schema generation more modular, testable, and easier to profile. I'd like to eventually work towards a situation in which it's easy to generate a GraphQL schema parser *in isolation*, without being connected to a database, and then parse a GraphQL query *in isolation*, without even listening any HTTP port. It is important that both of these operations can be examined in detail, and in isolation, since they are two major performance bottlenecks, as well as phases where many important upcoming features hook into. Implementation The following have been removed: - The entirety of `server/src-lib/Hasura/GraphQL/Execute/Plan.hs` - The core phases of query parsing and execution no longer have any references to query plan caching. Note that this is not to be confused with query *response* caching, which is not affected by this PR. This includes removal of the types: - - `Opaque`, which is replaced by a tuple. Note that the old implementation was broken and did not adequately hide the constructors. - - `QueryReusability` (and the `markNotReusable` method). Notably, the implementation of the `ParseT` monad now consists of two, rather than three, monad transformers. - Cache-related tests (in `server/src-test/Hasura/CacheBoundedSpec.hs`) have been removed . - References to query plan caching in the documentation. - The `planCacheOptions` in the `TenantConfig` type class was removed. However, during parsing, unrecognized fields in the YAML config get ignored, so this does not cause a breaking change. (Confirmed manually, as well as in consultation with @sordina.) - The metrics no longer send cache hit/miss messages. There are a few places in which one can still find references to query plan caching: - We still accept the `--query-plan-cache-size` command-line option for backwards compatibility. The `HASURA_QUERY_PLAN_CACHE_SIZE` environment variable is not read. https://github.com/hasura/graphql-engine-mono/pull/1815 GitOrigin-RevId: 17d92b254ec093c62a7dfeec478658ede0813eb7
2021-07-27 14:51:52 +03:00
-> m (Parser 'Both n (ValueWithOrigin (ColumnValue b)))
-- | The "path" argument for json column fields
jsonPathArg
:: MonadParse n
=> ColumnType b
-> InputFieldsParser n (Maybe (IR.ColumnOp b))
orderByOperators
:: NonEmpty (Definition EnumValueInfo, (BasicOrderType b, NullsOrderType b))
comparisonExps
:: MonadBuildSchema b r m n
=> ColumnType b
-> m (Parser 'Input n [ComparisonExp b])
updateOperators
:: (MonadSchema n m, MonadTableInfo r m)
=> TableInfo b
-> UpdPermInfo b
-> m (Maybe (InputFieldsParser n [(Column b, IR.UpdOpExpG (UnpreparedValue b))]))
mkCountType :: Maybe Bool -> Maybe [Column b] -> CountType b
aggregateOrderByCountType :: ScalarType b
-- | Computed field parser
computedField
:: MonadBuildSchema b r m n
=> SourceName
-> ComputedFieldInfo b
-> TableName b
-> SelPermInfo b
-> m (Maybe (FieldParser n (AnnotatedField b)))
-- | The 'node' root field of a Relay request.
node
:: MonadBuildSchema b r m n
=> m (Parser 'Output n (HashMap (TableName b) (SourceName, SourceConfig b, SelPermInfo b, PrimaryKeyColumns b, AnnotatedFields b)))
-- SQL literals
columnDefaultValue :: Column b -> SQLExpression b
type ComparisonExp b = OpExpG b (UnpreparedValue b)
data BackendExtension b = BackendExtension
{ backendRelay :: Maybe (XRelay b)
, backendNodesAgg :: Maybe (XNodesAgg b)
}