Skip to content
#

schema

Here are 1,652 public repositories matching this topic...

mausch
mausch commented Apr 2, 2020

The title might seem a bit vague but I don't know how to describe it any better tbh :-)

Anyway this is what happened: I got some 500 responses from the schema registry and all I could see in the logs was :

[2020-04-02 16:03:35,048] INFO 100.96.14.58 - - [02/Apr/2020:16:03:34 +0000] "PUT /config/some-topic-value HTTP/1.1" 500 69  502 (io.confluent.rest-utils.requests)

The logs di

bytebase
tianzhou
tianzhou commented Jul 30, 2021

Describe the bug

Unnecessary text explaining the project migration history maximum display count when there is no migration history at all.

Steps or screenshots to reproduce the behavior

  1. Go to a project where none of its database contain migration history (e.g. a new project), and click "Migration History"
  2. It displays a label "For database having migration history, we list up
aldeed
aldeed commented Aug 29, 2013

Add some validation checks for mongo operators that can't be done by SimpleSchema. See longshotlabs/meteor-simple-schema#9.

  • $rename (make sure existing values for the renamed key validate for the new key name)
  • $inc (check min/max and allowed values)
  • $addToSet (check maxCount)
  • $push (check maxCount)
  • $pull (check minCount)
  • $pullAll (check minCount)
  • $pop (check min
grmoon
grmoon commented Aug 13, 2021

Describe your problem

When users run a mutator (e.g. set-annotations), the output doesn't tell them which files changed. The only way a user can figure out which files were affected is by looking through them manually or doing git status or however they might normally be notified of changes to files.

It would be nice if we were able to notify the user which files changed as a result

Improve this page

Add a description, image, and links to the schema topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the schema topic, visit your repo's landing page and select "manage topics."

Learn more