Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / hortonworks/registry issues and pull requests
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#532 - AvroSchemaResolver goes into infinate loop if a schema incudes another that self references
Issue -
State: closed - Opened by potatop over 5 years ago
- 1 comment
#531 - Support Java 11
Issue -
State: open - Opened by potatop over 5 years ago
Labels: question
#531 - Support Java 11
Issue -
State: open - Opened by potatop over 5 years ago
Labels: question
#531 - Support Java 11
Issue -
State: open - Opened by potatop over 5 years ago
Labels: question
#531 - Support Java 11
Issue -
State: open - Opened by potatop over 5 years ago
Labels: question
#531 - Support Java 11
Issue -
State: open - Opened by potatop over 5 years ago
Labels: question
#531 - Support Java 11
Issue -
State: open - Opened by potatop over 5 years ago
Labels: question
#531 - Support Java 11
Issue -
State: open - Opened by potatop over 5 years ago
Labels: question
#523 - Error while running Bootstrap script
Issue -
State: closed - Opened by arcticOak2 over 5 years ago
- 1 comment
#523 - Error while running Bootstrap script
Issue -
State: closed - Opened by arcticOak2 over 5 years ago
- 1 comment
#523 - Error while running Bootstrap script
Issue -
State: closed - Opened by arcticOak2 over 5 years ago
- 1 comment
#523 - Error while running Bootstrap script
Issue -
State: closed - Opened by arcticOak2 over 5 years ago
- 1 comment
#523 - Error while running Bootstrap script
Issue -
State: closed - Opened by arcticOak2 over 5 years ago
- 1 comment
#523 - Error while running Bootstrap script
Issue -
State: closed - Opened by arcticOak2 over 5 years ago
- 1 comment
#522 - failed to create mysql table
Issue -
State: closed - Opened by melin almost 6 years ago
- 3 comments
#522 - failed to create mysql table
Issue -
State: closed - Opened by melin almost 6 years ago
- 3 comments
#522 - failed to create mysql table
Issue -
State: closed - Opened by melin almost 6 years ago
- 3 comments
#522 - failed to create mysql table
Issue -
State: closed - Opened by melin almost 6 years ago
- 3 comments
#522 - failed to create mysql table
Issue -
State: closed - Opened by melin almost 6 years ago
- 3 comments
#522 - failed to create mysql table
Issue -
State: closed - Opened by melin almost 6 years ago
- 3 comments
#521 - SchemaRegistryClient static block can throw exception causing NoClassDefFound
Issue -
State: closed - Opened by bbende almost 6 years ago
- 3 comments
#521 - SchemaRegistryClient static block can throw exception causing NoClassDefFound
Issue -
State: closed - Opened by bbende almost 6 years ago
- 3 comments
#521 - SchemaRegistryClient static block can throw exception causing NoClassDefFound
Issue -
State: closed - Opened by bbende almost 6 years ago
- 3 comments
#521 - SchemaRegistryClient static block can throw exception causing NoClassDefFound
Issue -
State: closed - Opened by bbende almost 6 years ago
- 3 comments
#521 - SchemaRegistryClient static block can throw exception causing NoClassDefFound
Issue -
State: closed - Opened by bbende almost 6 years ago
- 3 comments
#521 - SchemaRegistryClient static block can throw exception causing NoClassDefFound
Issue -
State: closed - Opened by bbende almost 6 years ago
- 3 comments
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#520 - schema-registry-core: produce a separate artifact containing core library only
Issue -
State: closed - Opened by bitbrain almost 6 years ago
- 1 comment
#515 - Address CVE-2018-11771 vulnerability by upgrading commons-compress lib.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#515 - Address CVE-2018-11771 vulnerability by upgrading commons-compress lib.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#515 - Address CVE-2018-11771 vulnerability by upgrading commons-compress lib.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#515 - Address CVE-2018-11771 vulnerability by upgrading commons-compress lib.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#515 - Address CVE-2018-11771 vulnerability by upgrading commons-compress lib.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#515 - Address CVE-2018-11771 vulnerability by upgrading commons-compress lib.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#515 - Address CVE-2018-11771 vulnerability by upgrading commons-compress lib.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#515 - Address CVE-2018-11771 vulnerability by upgrading commons-compress lib.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#515 - Address CVE-2018-11771 vulnerability by upgrading commons-compress lib.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#512 - record without matched schema
Issue -
State: closed - Opened by mazorigal almost 6 years ago
- 1 comment
Labels: question
#511 - Add a UI control in SR to call delete API to delete a given schema
Issue -
State: open - Opened by priyank5485 almost 6 years ago
- 1 comment
Labels: enhancement
#511 - Add a UI control in SR to call delete API to delete a given schema
Issue -
State: open - Opened by priyank5485 almost 6 years ago
- 1 comment
Labels: enhancement
#511 - Add a UI control in SR to call delete API to delete a given schema
Issue -
State: open - Opened by priyank5485 almost 6 years ago
- 1 comment
Labels: enhancement
#511 - Add a UI control in SR to call delete API to delete a given schema
Issue -
State: open - Opened by priyank5485 almost 6 years ago
- 1 comment
Labels: enhancement
#511 - Add a UI control in SR to call delete API to delete a given schema
Issue -
State: open - Opened by priyank5485 almost 6 years ago
- 1 comment
Labels: enhancement
#511 - Add a UI control in SR to call delete API to delete a given schema
Issue -
State: open - Opened by priyank5485 almost 6 years ago
- 1 comment
Labels: enhancement
#511 - Add a UI control in SR to call delete API to delete a given schema
Issue -
State: open - Opened by priyank5485 almost 6 years ago
- 1 comment
Labels: enhancement
#511 - Add a UI control in SR to call delete API to delete a given schema
Issue -
State: open - Opened by priyank5485 almost 6 years ago
- 1 comment
Labels: enhancement
#509 - Provide a delete API for deleting a schema metadata and all related information
Issue -
State: closed - Opened by priyank5485 almost 6 years ago
- 6 comments
#509 - Provide a delete API for deleting a schema metadata and all related information
Issue -
State: closed - Opened by priyank5485 almost 6 years ago
- 6 comments
#509 - Provide a delete API for deleting a schema metadata and all related information
Issue -
State: closed - Opened by priyank5485 almost 6 years ago
- 6 comments
#509 - Provide a delete API for deleting a schema metadata and all related information
Issue -
State: closed - Opened by priyank5485 almost 6 years ago
- 6 comments
#509 - Provide a delete API for deleting a schema metadata and all related information
Issue -
State: closed - Opened by priyank5485 almost 6 years ago
- 6 comments
#509 - Provide a delete API for deleting a schema metadata and all related information
Issue -
State: closed - Opened by priyank5485 almost 6 years ago
- 6 comments
#509 - Provide a delete API for deleting a schema metadata and all related information
Issue -
State: closed - Opened by priyank5485 almost 6 years ago
- 6 comments
#509 - Provide a delete API for deleting a schema metadata and all related information
Issue -
State: closed - Opened by priyank5485 almost 6 years ago
- 6 comments
#506 - Several CVEs reported because of hadoop-client lib dependency.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#506 - Several CVEs reported because of hadoop-client lib dependency.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#506 - Several CVEs reported because of hadoop-client lib dependency.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#506 - Several CVEs reported because of hadoop-client lib dependency.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#506 - Several CVEs reported because of hadoop-client lib dependency.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#506 - Several CVEs reported because of hadoop-client lib dependency.
Issue -
State: closed - Opened by satishd almost 6 years ago
- 1 comment
#498 - Feature request: allow us to reference schemas within other schemas
Issue -
State: open - Opened by dmsolow about 6 years ago
- 6 comments
Labels: enhancement, question
#498 - Feature request: allow us to reference schemas within other schemas
Issue -
State: open - Opened by dmsolow about 6 years ago
- 6 comments
Labels: enhancement, question
#498 - Feature request: allow us to reference schemas within other schemas
Issue -
State: open - Opened by dmsolow about 6 years ago
- 6 comments
Labels: enhancement, question
#498 - Feature request: allow us to reference schemas within other schemas
Issue -
State: open - Opened by dmsolow about 6 years ago
- 6 comments
Labels: enhancement, question
#498 - Feature request: allow us to reference schemas within other schemas
Issue -
State: open - Opened by dmsolow about 6 years ago
- 6 comments
Labels: enhancement, question
#498 - Feature request: allow us to reference schemas within other schemas
Issue -
State: open - Opened by dmsolow about 6 years ago
- 6 comments
Labels: enhancement, question
#498 - Feature request: allow us to reference schemas within other schemas
Issue -
State: open - Opened by dmsolow about 6 years ago
- 6 comments
Labels: enhancement, question
#497 - The registry doesn't create a new schema version if the field's logicalType changed
Issue -
State: open - Opened by rvh about 6 years ago
- 2 comments
Labels: bug
#497 - The registry doesn't create a new schema version if the field's logicalType changed
Issue -
State: open - Opened by rvh about 6 years ago
- 2 comments
Labels: bug
#497 - The registry doesn't create a new schema version if the field's logicalType changed
Issue -
State: open - Opened by rvh about 6 years ago
- 2 comments
Labels: bug
#497 - The registry doesn't create a new schema version if the field's logicalType changed
Issue -
State: open - Opened by rvh about 6 years ago
- 2 comments
Labels: bug
#497 - The registry doesn't create a new schema version if the field's logicalType changed
Issue -
State: open - Opened by rvh about 6 years ago
- 2 comments
Labels: bug
#497 - The registry doesn't create a new schema version if the field's logicalType changed
Issue -
State: open - Opened by rvh about 6 years ago
- 2 comments
Labels: bug
#497 - The registry doesn't create a new schema version if the field's logicalType changed
Issue -
State: open - Opened by rvh about 6 years ago
- 2 comments
Labels: bug
#492 - Update spring-context to 5.0.7.RELEASE
Issue -
State: closed - Opened by satishd about 6 years ago
- 1 comment