Skip to content
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

API breaking changes for 0.19.0 #934

Closed
16 of 17 tasks
etiennedi opened this issue Jul 31, 2019 · 0 comments · Fixed by #938
Closed
16 of 17 tasks

API breaking changes for 0.19.0 #934

etiennedi opened this issue Jul 31, 2019 · 0 comments · Fixed by #938

Comments

@etiennedi
Copy link
Member

etiennedi commented Jul 31, 2019

As part of the new release 0.19.0 we want to group a lot of breaking changes in our API, so that we can then stay stable for a long time after that.

Todos

  • /meta does not return schema
  • /meta should display
    • version number
    • c11y version number
    • (optional p2p info)
    • number of words in contextionary
  • ref can either be beacon type or fuzzy concept type
    • concept type will fail with "not supported yet"
  • in GQL ...on Beacon reference is available
    • no implementation yet
  • in cross-ref creation $cref becomes beacon
  • API base weaviate/v1 becomes just v1
  • in GQL GetMeta renamed to Meta
  • SUGGESTION: Group entities when recognized #919 add Merge/Group to API
    • first iteration (separate Meta API)
    • second iteration (as discussed Fri, August 2), no separate API
  • In RESTful API, crefs should always be represented in an array regardless of cardinality #871 always use array for cross-refs
etiennedi added a commit that referenced this issue Jul 31, 2019
etiennedi added a commit that referenced this issue Aug 1, 2019
etiennedi added a commit that referenced this issue Aug 1, 2019
etiennedi added a commit that referenced this issue Aug 1, 2019
etiennedi added a commit that referenced this issue Aug 2, 2019
after changed requirements.
etiennedi added a commit that referenced this issue Aug 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant