Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Avoid deprecated nameResolverFactory

Open
  • Is something wrong?
#296 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Stale
Tech stack
grpc, scala
Domain
api

Research direction

Start with runtime/src/main/scala/org/apache/pekko/grpc/internal/NettyClientUtils.scala, especially the name-resolver code around lines 49–64. Compare it with the linked grpc-java NameResolveClient example and the proposed NameResolverRegistry registration. Done means the deprecated nameResolverFactory usage is replaced without changing the resolver settings passed to PekkoDiscoveryNameResolverProvider.

Written by the indexing model from the issue text.

Description

I was reading the code for name solver and found a todo item, hoping to resolve it.

motivation

same issue in akka-grpc https://github.com/akka/akka-grpc/issues/1092

code in pekko org.apache.pekko.grpc.internal.NettyClientUtils

https://github.com/apache/pekko-grpc/blob/7f4b94cf7200be1506449da86d5811246c87af0d/runtime/src/main/scala/org/apache/pekko/grpc/internal/NettyClientUtils.scala#L49-L64

changes

according to grpc-java

https://github.com/grpc/grpc-java/blob/497e1552172632107574d67d7c092a3f5a39a980/examples/src/main/java/io/grpc/examples/nameresolve/NameResolveClient.java#L39

we just need

NameResolverRegistry.getDefaultRegistry.register(
      new PekkoDiscoveryNameResolverProvider(
        settings.serviceDiscovery,
        settings.defaultPort,
        settings.serviceName,
        settings.servicePortName,
        settings.serviceProtocol,
        settings.resolveTimeout))
Dominant language
Scala
Stars
55
Forks
30
Avg merge
1d 18h
Merged PRs (30d)
19

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/pekko-grpc

All issues in apache/pekko-grpc

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.