You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Ken Hu (Jira)" <ji...@apache.org> on 2026/07/16 15:22:00 UTC

[jira] [Commented] (TINKERPOP-3258) Remove support for custom request serializer settings

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

Ken Hu commented on TINKERPOP-3258:
-----------------------------------

Completed as part of https://github.com/apache/tinkerpop/pull/3492 and https://github.com/apache/tinkerpop/pull/3447

> Remove support for custom request serializer settings
> -----------------------------------------------------
>
>                 Key: TINKERPOP-3258
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-3258
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: driver
>    Affects Versions: 4.0.0
>            Reporter: Ken Hu
>            Priority: Major
>             Fix For: 4.0.0
>
>
> In 4.x, interceptors allow the user to make any changes to the body that they want. This feature should allow the user to manual update the content-encoding header and the request body to allow for custom serialization. This should be the preferred method as by default we want the GLVs to serialize using plain JSON now.



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