Java-Core to Gax Mapping Tracking Ticket

未关闭
#13,297 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
重构
描述清晰度
需要澄清
活跃度
冷清
技术栈
java

调研方向

首先比较列出的 Java-Core 和 Gax 领域:ServiceOptions 与 ClientSettings、Resolve Host 与 EndpointContext,以及 DirectExector 与 ScheduledExectuor。该 issue 未指定文件或测试;要完成此任务,需要定义并实现一个完整的映射,同时不破坏现有的手写客户端库。

由索引模型根据 Issue 内容生成。

描述

priority: p2 type: feature request

Problem

The Java SDK has a split in some runtime functionality between Java-Core and Gax for some client libraries. Historically Java-Core was maintained by older handwritten teams and contains mostly the same functionality that exists inside Gax. Gax is modern and actively maintained by the Cloud Java team and to ensure that features have complete coverage in the Java SDK, the features must be added to both Java-Core and Gax. We cannot get rid of Java-Core without potential breaking changes and migrating all use cases to Gax may not also be possible.

Solution(s)?

  1. Java-Core's functionality serves as a wrapper around Gax that is used for older, existing handwritten libraries. Java-Core should delegate the actual logic to Gax so that there is a single source of truth. Changes required from new features should only be made to Gax and can be applied to all the client libraries in the SDK.

Areas to consider creating a mapping

  1. Settings/ Options (ServiceOptions -> ClientSettings)
  2. URL Resolution (Resolve Host -> EndpointContext)
  3. Executor logic (Deprecation of DirectExector and replace with ScheduledExectuor)?
主要语言
Java
星标
2.1k
派生
1.2k
平均合并
2 天 14 小时
30 天内合并 PR
192

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

googleapis/google-cloud-java 的其他 Issue

查看 googleapis/google-cloud-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。