Michael André Pearce

@satishd see google group, just want to discuss a release cadence, rather than having big feature releases, i want to propose a monthly release. For example i can see us...

Re ranges, for the immediate interim of just getting confluent repo ingested without collision. Currently for nextId it relies on the underlying db's auto increment feature and null id is...

@satishd @harshach forgot to ping you for the above comment, any thoughts?

+1 I like this idea, very useful.

@satishd @harshach to do this rather than having to a bunch of dirty dependency excludes, i am thinking of splitting the common module into: - common-client - common-server where common-server...

+1 One main point is that the numerical ids generated and used in serialised data must remain globally unique (as these globally identify the schema once registered irrespective of group...

@harshach to achieve this https://github.com/hortonworks/registry/issues/166, i was thinking of making this just call the rest endpoint, and even to make it so its manually invoked as the initial solution. So...

@satishd An idea i just had, would be a bit like in https://github.com/hortonworks/registry/issues/166 I'm suggesting essentially we assume confluent repo could have a configurable reserved range, e.g. in that a...

Any update here? we are a confluent customer.

@mahajanadhitya just checking in if there is any update here?