这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@abooij
Copy link
Contributor

@abooij abooij commented Nov 2, 2020

Description

This is an incremental PR towards #5797. As part of that work, the post-PDV schema generation was improved, in an attempt to improve efficiency of server startup and schema reloading. This PR is a rebase of commit be84310 onto master so that it can hopefully be merged separately.

Changelog

  • CHANGELOG.md is updated with user-facing content relevant to this PR. If no changelog is required, then add the no-changelog-required label.

Affected components

  • Server

Related Issues

Solution and Design

Steps to test and verify

Limitations, known bugs & workarounds

Server checklist

Catalog upgrade

Does this PR change Hasura Catalog version?

  • No

Metadata

Does this PR add a new Metadata feature?

  • No

GraphQL

  • No new GraphQL schema is generated

Breaking changes

  • No Breaking changes

@netlify
Copy link

netlify bot commented Nov 2, 2020

Deploy preview for hasura-docs ready!

Built with commit 4b66dbf

https://deploy-preview-6116--hasura-docs.netlify.app

@abooij abooij marked this pull request as ready for review November 3, 2020 10:12
@abooij abooij requested a review from a team as a code owner November 3, 2020 10:12
CHANGELOG.md Outdated
- server: fix issue with tracking custom functions that return `SETOF` materialized view (close #5294) (#5945)
- server: introduce optional custom table name in table configuration to track the table according to the custom name. The `set_table_custom_fields` API has been deprecated, A new API `set_table_customization` has been added to set the configuration. (#3811)
- server: allow remote relationships with union, interface and enum type fields as well (fixes #5875) (#6080)
- server: clean up the post-PDV schema generation (#6116)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel we do not need a changelog for this as it is kinda vague and definitely not user understandable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect. I was on the fence myself.

Copy link
Member

@0x777 0x777 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not a big fan of how we check for remote schema field conflicts with those derived from tracking tables/functions. We can however defer this to later.

Co-authored-by: Vamshi Surabhi <0x777@users.noreply.github.com>
Copy link
Contributor

@tirumaraiselvan tirumaraiselvan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no CL required

@kodiakhq kodiakhq bot merged commit fd8d51a into hasura:master Nov 3, 2020
scriptonist pushed a commit to scriptonist/graphql-engine that referenced this pull request Nov 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants