[ 
https://issues.apache.org/jira/browse/SPARK-50737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hyukjin Kwon resolved SPARK-50737.
----------------------------------
    Resolution: Invalid

Resolving as Invalid: this is a usage/how-to question rather than a report of a 
specific Spark defect or a concrete change proposal. Apache Spark uses JIRA to 
track bugs and improvements; usage questions are best asked on the 
[email protected] mailing list (https://spark.apache.org/community.html) or 
Stack Overflow (tag apache-spark), where a wider audience can help. Please 
re-open with a concrete reproducer or a specific proposed code/doc change if 
this is actually a bug or an actionable improvement. Thanks!

> Plans for Integrating HMS 4.0 `_req` Methods in Apache Spark
> ------------------------------------------------------------
>
>                 Key: SPARK-50737
>                 URL: https://issues.apache.org/jira/browse/SPARK-50737
>             Project: Spark
>          Issue Type: Question
>          Components: Spark Core
>    Affects Versions: 3.5.4, 3.5.5
>            Reporter: Anurag Kumar Dwivedi
>            Priority: Major
>
> I’m reaching out to inquire about Apache Spark’s plans to support the new set 
> of methods introduced in HMS 4.0. These methods (e.g., 
> {{{}get_database_req{}}}) are designed to be future-oriented as they accept a 
> request body instead of traditional parameters.
> As these changes are critical for compatibility and leveraging the latest HMS 
> features, it would be helpful to understand:
>  # Is there an existing plan or timeline for implementing support for these 
> methods in Apache Spark?
>  # Are there any ongoing discussions or workarounds currently available for 
> integrating these methods in Spark?
> Thank you for your time and for all the incredible work on Spark!
> Looking forward to hearing from the community.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to