[ 
https://issues.apache.org/jira/browse/TINKERPOP-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066989#comment-18066989
 ] 

ASF GitHub Bot commented on TINKERPOP-3237:
-------------------------------------------

codecov-commenter commented on PR #3335:
URL: https://github.com/apache/tinkerpop/pull/3335#issuecomment-4096688802

   ## 
[Codecov](https://app.codecov.io/gh/apache/tinkerpop/pull/3335?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)
 Report
   :white_check_mark: All modified and coverable lines are covered by tests.
   :warning: Please [upload](https://docs.codecov.com/docs/codecov-uploader) 
report for BASE (`3.8-dev@81073ea`). [Learn 
more](https://docs.codecov.io/docs/error-reference?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#section-missing-base-commit)
 about missing BASE report.
   
   <details><summary>Additional details and impacted files</summary>
   
   
   
   ```diff
   @@            Coverage Diff             @@
   ##             3.8-dev    #3335   +/-   ##
   ==========================================
     Coverage           ?   79.08%           
   ==========================================
     Files              ?       28           
     Lines              ?     6020           
     Branches           ?        0           
   ==========================================
     Hits               ?     4761           
     Misses             ?     1032           
     Partials           ?      227           
   ```
   </details>
   
   [:umbrella: View full report in Codecov by 
Sentry](https://app.codecov.io/gh/apache/tinkerpop/pull/3335?dropdown=coverage&src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).
   
   :loudspeaker: Have feedback on the report? [Share it 
here](https://about.codecov.io/codecov-pr-comment-feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).
   <details><summary> :rocket: New features to boost your workflow: </summary>
   
   - :snowflake: [Test 
Analytics](https://docs.codecov.com/docs/test-analytics): Detect flaky tests, 
report on failures, and find test suite problems.
   - :package: [JS Bundle 
Analysis](https://docs.codecov.com/docs/javascript-bundle-analysis): Save 
yourself from yourself by tracking and limiting bundle sizes in JS merges.
   </details>




> Add Custom Type Writer/Serializer API for gremlin-go
> ----------------------------------------------------
>
>                 Key: TINKERPOP-3237
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-3237
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: go
>    Affects Versions: 3.8.0
>            Reporter: Haiyu Wang
>            Priority: Major
>             Fix For: 3.8.1
>
>
> ## Problem
>  
> Currently, gremlin-go supports deserializing custom types via 
> `RegisterCustomTypeReader()`, but lacks the corresponding functionality to 
> serialize custom types when sending requests to the server. This creates an 
> asymmetry where users can read custom types from server responses but cannot 
> write them in requests.
> **The Java driver already has complete custom type support** through 
> `CustomTypeSerializer` in `GraphBinaryWriter.java` and 
> `GraphBinaryReader.java`. This gap prevents gremlin-go users from working 
> with custom types in graph databases like JanusGraph, which use custom types 
> such as `RelationIdentifier`, `Geoshape`, etc.
> ## Current State
> - **Java driver**: ✅ Custom Type Reader + ✅ Custom Type Writer
> - **gremlin-go**: ✅ Custom Type Reader + ❌ Custom Type Writer (incomplete)
> ## Proposed Solution
> Add a `RegisterCustomTypeWriter()` API that mirrors the existing 
> `CustomTypeReader` pattern and implements the same GraphBinary custom type 
> format used by the Java driver.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to