jgroups-extras / jgroups-extras/jgroups-mongo
Review whether it makes sense to extend JDBC_PING2 in the first place
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 2
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 3
Description
Review what are we getting from extending JDBC_PING2 in the first place.
This is very problematic because the protocol inherits a lot of SQL-specific properties from JDBC_PING2, insert_single_sql, jndi names, datasources, etc. that are NOT usable.
The price we pay is fragility and tight coupling to a JGroups version.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the current JDBC_PING2 extension and tracing its use of insert_single_sql, JNDI names, and datasources. Done means reaching a maintainer-backed decision on whether the inheritance should remain and recording the resulting scope; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mongodb
- Domain
- databases, distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100