Re: [PR] [MINOR][SQL] Remove outdated `TODO`s from `UnsafeHashedRelation` [spark]

2024-06-04 Thread via GitHub


LuciferYang closed pull request #46736: [MINOR][SQL] Remove outdated `TODO`s 
from `UnsafeHashedRelation`
URL: https://github.com/apache/spark/pull/46736


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org



Re: [PR] [MINOR][SQL] Remove outdated `TODO`s from `UnsafeHashedRelation` [spark]

2024-05-26 Thread via GitHub


LuciferYang commented on code in PR #46736:
URL: https://github.com/apache/spark/pull/46736#discussion_r1615495409


##
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/HashedRelation.scala:
##
@@ -409,9 +407,6 @@ private[joins] class UnsafeHashedRelation(
 val pageSizeBytes = Option(SparkEnv.get).map(_.memoryManager.pageSizeBytes)
   .getOrElse(new SparkConf().get(BUFFER_PAGESIZE).getOrElse(16L * 1024 * 
1024))
 
-// TODO(josh): We won't need this dummy memory manager after future 
refactorings; revisit

Review Comment:
   Thank you for your explanation. So, do we have a more suitable way to 
re-describe this TODO? We can change to truly track it by creating a Jira and 
updating the TODO description.
   
   



##
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/HashedRelation.scala:
##
@@ -409,9 +407,6 @@ private[joins] class UnsafeHashedRelation(
 val pageSizeBytes = Option(SparkEnv.get).map(_.memoryManager.pageSizeBytes)
   .getOrElse(new SparkConf().get(BUFFER_PAGESIZE).getOrElse(16L * 1024 * 
1024))
 
-// TODO(josh): We won't need this dummy memory manager after future 
refactorings; revisit

Review Comment:
   Thank you for your explanation @JoshRosen . So, do we have a more suitable 
way to re-describe this TODO? We can change to truly track it by creating a 
Jira and updating the TODO description.
   
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org



Re: [PR] [MINOR][SQL] Remove outdated `TODO`s from `UnsafeHashedRelation` [spark]

2024-05-24 Thread via GitHub


JoshRosen commented on code in PR #46736:
URL: https://github.com/apache/spark/pull/46736#discussion_r1613884389


##
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/HashedRelation.scala:
##
@@ -409,9 +407,6 @@ private[joins] class UnsafeHashedRelation(
 val pageSizeBytes = Option(SparkEnv.get).map(_.memoryManager.pageSizeBytes)
   .getOrElse(new SparkConf().get(BUFFER_PAGESIZE).getOrElse(16L * 1024 * 
1024))
 
-// TODO(josh): We won't need this dummy memory manager after future 
refactorings; revisit

Review Comment:
   These are ancient TOODs, but my recollection is that they were related to 
some limitations in storage memory management related to transferring memory 
between execution and storage: at the time (and even now) I don't think we had 
a reliable way to transfer task-allocated memory pages into a shared context 
where they can be used by multiple tasks and counted towards storage memory, 
hence some of the hacks here.
   
   I'm not firmly opposed to removing TODOs like this, but I also don't 
particularly understand the motivation for doing so: sure, it's a bit of 
clutter in the code but if we're not replacing them with a newer comment or 
making a code change then it just seems like cleanup for cleanup's sake, which 
I am generally opposed to for code churn / review bandwidth reasons.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org



Re: [PR] [MINOR][SQL] Remove outdated `TODO`s from `UnsafeHashedRelation` [spark]

2024-05-24 Thread via GitHub


LuciferYang commented on code in PR #46736:
URL: https://github.com/apache/spark/pull/46736#discussion_r1613184450


##
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/HashedRelation.scala:
##
@@ -409,9 +407,6 @@ private[joins] class UnsafeHashedRelation(
 val pageSizeBytes = Option(SparkEnv.get).map(_.memoryManager.pageSizeBytes)
   .getOrElse(new SparkConf().get(BUFFER_PAGESIZE).getOrElse(16L * 1024 * 
1024))
 
-// TODO(josh): We won't need this dummy memory manager after future 
refactorings; revisit

Review Comment:
   friendly ping @JoshRosen , can we remove these 2 TODO?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org



Re: [PR] [MINOR][SQL] Remove outdated `TODO`s from `UnsafeHashedRelation` [spark]

2024-05-24 Thread via GitHub


LuciferYang commented on code in PR #46736:
URL: https://github.com/apache/spark/pull/46736#discussion_r1613184450


##
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/HashedRelation.scala:
##
@@ -409,9 +407,6 @@ private[joins] class UnsafeHashedRelation(
 val pageSizeBytes = Option(SparkEnv.get).map(_.memoryManager.pageSizeBytes)
   .getOrElse(new SparkConf().get(BUFFER_PAGESIZE).getOrElse(16L * 1024 * 
1024))
 
-// TODO(josh): We won't need this dummy memory manager after future 
refactorings; revisit

Review Comment:
   friendly ping @JoshRosen , can we remove these 2 TOOD?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org