Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / pravega/schema-registry issues and pull requests

#244 - Prepare schema-registry for release 0.4

Issue - State: closed - Opened by RaulGracia over 2 years ago

#244 - Prepare schema-registry for release 0.4

Issue - State: closed - Opened by RaulGracia over 2 years ago

#243 - Issue 242: Update Third Party Library Versions

Pull Request - State: closed - Opened by shshashwat over 2 years ago - 4 comments

#243 - Issue 242: Update Third Party Library Versions

Pull Request - State: closed - Opened by shshashwat over 2 years ago - 4 comments

#243 - Issue 242: Update Third Party Library Versions

Pull Request - State: closed - Opened by shshashwat over 2 years ago - 4 comments

#243 - Issue 242: Update Third Party Library Versions

Pull Request - State: closed - Opened by shshashwat over 2 years ago - 4 comments

#242 - Upgrade Third Party components in Schema-Registry

Issue - State: closed - Opened by shshashwat over 2 years ago
Labels: area/license, Priority/P1

#242 - Upgrade Third Party components in Schema-Registry

Issue - State: closed - Opened by shshashwat over 2 years ago
Labels: area/license, Priority/P1

#242 - Upgrade Third Party components in Schema-Registry

Issue - State: closed - Opened by shshashwat over 2 years ago
Labels: area/license, Priority/P1

#242 - Upgrade Third Party components in Schema-Registry

Issue - State: closed - Opened by shshashwat over 2 years ago
Labels: area/license, Priority/P1

#242 - Upgrade Third Party components in Schema-Registry

Issue - State: closed - Opened by shshashwat over 2 years ago
Labels: area/license, Priority/P1

#241 - Issue 240: Remove Netty dependencies

Pull Request - State: closed - Opened by shshashwat over 2 years ago - 3 comments

#241 - Issue 240: Remove Netty dependencies

Pull Request - State: closed - Opened by shshashwat over 2 years ago - 3 comments

#241 - Issue 240: Remove Netty dependencies

Pull Request - State: closed - Opened by shshashwat over 2 years ago - 3 comments

#240 - Update build.gradle file to resolve netty issues

Issue - State: closed - Opened by shshashwat over 2 years ago

#240 - Update build.gradle file to resolve netty issues

Issue - State: closed - Opened by shshashwat over 2 years ago

#240 - Update build.gradle file to resolve netty issues

Issue - State: closed - Opened by shshashwat over 2 years ago

#239 - Issue 238: Convert markdown to support Docusaurus and combined docs repo

Pull Request - State: open - Opened by derekm almost 3 years ago

#239 - Issue 238: Convert markdown to support Docusaurus and combined docs repo

Pull Request - State: open - Opened by derekm almost 3 years ago

#239 - Issue 238: Convert markdown to support Docusaurus and combined docs repo

Pull Request - State: open - Opened by derekm almost 3 years ago

#238 - Convert docs to Docusaurus

Issue - State: open - Opened by derekm almost 3 years ago

#238 - Convert docs to Docusaurus

Issue - State: open - Opened by derekm almost 3 years ago

#238 - Convert docs to Docusaurus

Issue - State: open - Opened by derekm almost 3 years ago

#238 - Convert docs to Docusaurus

Issue - State: open - Opened by derekm almost 3 years ago

#238 - Convert docs to Docusaurus

Issue - State: open - Opened by derekm almost 3 years ago

#237 - Issue 234: Update branch version to 0.3.0 in r0.3 branch

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#237 - Issue 234: Update branch version to 0.3.0 in r0.3 branch

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#236 - Issue 235: Upgrade Schema Registry version to 0.4.0-SNAPSHOT

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#236 - Issue 235: Upgrade Schema Registry version to 0.4.0-SNAPSHOT

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#236 - Issue 235: Upgrade Schema Registry version to 0.4.0-SNAPSHOT

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#236 - Issue 235: Upgrade Schema Registry version to 0.4.0-SNAPSHOT

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#236 - Issue 235: Upgrade Schema Registry version to 0.4.0-SNAPSHOT

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#235 - Promote master to 0.4-Snapshot

Issue - State: closed - Opened by shrids about 3 years ago

#235 - Promote master to 0.4-Snapshot

Issue - State: closed - Opened by shrids about 3 years ago

#235 - Promote master to 0.4-Snapshot

Issue - State: closed - Opened by shrids about 3 years ago

#235 - Promote master to 0.4-Snapshot

Issue - State: closed - Opened by shrids about 3 years ago

#235 - Promote master to 0.4-Snapshot

Issue - State: closed - Opened by shrids about 3 years ago

#235 - Promote master to 0.4-Snapshot

Issue - State: closed - Opened by shrids about 3 years ago

#234 - Set version to 0.3.0 in r0.3 branch

Issue - State: closed - Opened by shrids about 3 years ago

#234 - Set version to 0.3.0 in r0.3 branch

Issue - State: closed - Opened by shrids about 3 years ago

#234 - Set version to 0.3.0 in r0.3 branch

Issue - State: closed - Opened by shrids about 3 years ago

#234 - Set version to 0.3.0 in r0.3 branch

Issue - State: closed - Opened by shrids about 3 years ago

#233 - Update Gradle version in Schema-Registry

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: enhancement

#233 - Update Gradle version in Schema-Registry

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: enhancement

#233 - Update Gradle version in Schema-Registry

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: enhancement

#233 - Update Gradle version in Schema-Registry

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: enhancement

#233 - Update Gradle version in Schema-Registry

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: enhancement

#232 - Issue 231: Prepare for 0.3.0 release

Pull Request - State: closed - Opened by shrids about 3 years ago - 2 comments

#232 - Issue 231: Prepare for 0.3.0 release

Pull Request - State: closed - Opened by shrids about 3 years ago - 2 comments

#232 - Issue 231: Prepare for 0.3.0 release

Pull Request - State: closed - Opened by shrids about 3 years ago - 2 comments

#232 - Issue 231: Prepare for 0.3.0 release

Pull Request - State: closed - Opened by shrids about 3 years ago - 2 comments

#232 - Issue 231: Prepare for 0.3.0 release

Pull Request - State: closed - Opened by shrids about 3 years ago - 2 comments

#232 - Issue 231: Prepare for 0.3.0 release

Pull Request - State: closed - Opened by shrids about 3 years ago - 2 comments

#231 - Prepare schema-registry for release.

Issue - State: closed - Opened by shrids about 3 years ago

#231 - Prepare schema-registry for release.

Issue - State: closed - Opened by shrids about 3 years ago

#231 - Prepare schema-registry for release.

Issue - State: closed - Opened by shrids about 3 years ago

#231 - Prepare schema-registry for release.

Issue - State: closed - Opened by shrids about 3 years ago

#231 - Prepare schema-registry for release.

Issue - State: closed - Opened by shrids about 3 years ago

#231 - Prepare schema-registry for release.

Issue - State: closed - Opened by shrids about 3 years ago

#230 - Update SR config properties with correct auth token

Pull Request - State: closed - Opened by shshashwat about 3 years ago - 1 comment
Labels: bug, Priority/P1

#229 - Typo in schema-registry server conf

Issue - State: closed - Opened by fyang86 about 3 years ago - 1 comment
Labels: bug, Priority/P1

#229 - Typo in schema-registry server conf

Issue - State: closed - Opened by fyang86 about 3 years ago - 1 comment
Labels: bug, Priority/P1

#229 - Typo in schema-registry server conf

Issue - State: closed - Opened by fyang86 about 3 years ago - 1 comment
Labels: bug, Priority/P1

#229 - Typo in schema-registry server conf

Issue - State: closed - Opened by fyang86 about 3 years ago - 1 comment
Labels: bug, Priority/P1

#228 - Issue 227 add type in case it's not provided

Pull Request - State: open - Opened by shshashwat about 3 years ago - 4 comments

#228 - Issue 227 add type in case it's not provided

Pull Request - State: open - Opened by shshashwat about 3 years ago - 4 comments

#228 - Issue 227 add type in case it's not provided

Pull Request - State: open - Opened by shshashwat about 3 years ago - 4 comments

#227 - Error 504 in case of adding custom schema with no name/type

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: bug

#226 - Add logs

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#226 - Add logs

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#226 - Add logs

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#226 - Add logs

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#225 - Improve Logging on Schema Registry

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: enhancement

#225 - Improve Logging on Schema Registry

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: enhancement

#225 - Improve Logging on Schema Registry

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: enhancement

#225 - Improve Logging on Schema Registry

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: enhancement

#224 - Issue-223 Update Schema Registry release version

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#224 - Issue-223 Update Schema Registry release version

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#224 - Issue-223 Update Schema Registry release version

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#224 - Issue-223 Update Schema Registry release version

Pull Request - State: closed - Opened by shshashwat about 3 years ago

#222 - All Key-Value Tables must be accessed via the APIs in io.pravega.client.tables

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: enhancement

#222 - All Key-Value Tables must be accessed via the APIs in io.pravega.client.tables

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: enhancement

#222 - All Key-Value Tables must be accessed via the APIs in io.pravega.client.tables

Issue - State: open - Opened by shshashwat about 3 years ago
Labels: enhancement

#221 - Issue 209: Update Schema Registry to consume latest Pravega Client

Pull Request - State: closed - Opened by shshashwat about 3 years ago - 1 comment

#221 - Issue 209: Update Schema Registry to consume latest Pravega Client

Pull Request - State: closed - Opened by shshashwat about 3 years ago - 1 comment

#221 - Issue 209: Update Schema Registry to consume latest Pravega Client

Pull Request - State: closed - Opened by shshashwat about 3 years ago - 1 comment

#221 - Issue 209: Update Schema Registry to consume latest Pravega Client

Pull Request - State: closed - Opened by shshashwat about 3 years ago - 1 comment

#220 - [issue-219] Fix Wrong commit number in snapshot version

Pull Request - State: closed - Opened by crazyzhou over 3 years ago

#220 - [issue-219] Fix Wrong commit number in snapshot version

Pull Request - State: closed - Opened by crazyzhou over 3 years ago

#220 - [issue-219] Fix Wrong commit number in snapshot version

Pull Request - State: closed - Opened by crazyzhou over 3 years ago

#220 - [issue-219] Fix Wrong commit number in snapshot version

Pull Request - State: closed - Opened by crazyzhou over 3 years ago

#220 - [issue-219] Fix Wrong commit number in snapshot version

Pull Request - State: closed - Opened by crazyzhou over 3 years ago

#220 - [issue-219] Fix Wrong commit number in snapshot version

Pull Request - State: closed - Opened by crazyzhou over 3 years ago

#220 - [issue-219] Fix Wrong commit number in snapshot version

Pull Request - State: closed - Opened by crazyzhou over 3 years ago

#219 - Wrong count number of the artifact

Issue - State: closed - Opened by crazyzhou over 3 years ago

#219 - Wrong count number of the artifact

Issue - State: closed - Opened by crazyzhou over 3 years ago

#219 - Wrong count number of the artifact

Issue - State: closed - Opened by crazyzhou over 3 years ago