[
https://issues.apache.org/jira/browse/BEAM-10514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165939#comment-17165939
]
Ning Kang commented on BEAM-10514:
----------------------------------
The fix is working for existing use cases.
Future todo item is to make sure the file path length will not exceed the
windows 260 character length limit when new features are added.
Keep the priority as P3 since the change is not urgent.
> Make sure Interactive Beam cache file path length does not exceed OS limits
> ---------------------------------------------------------------------------
>
> Key: BEAM-10514
> URL: https://issues.apache.org/jira/browse/BEAM-10514
> Project: Beam
> Issue Type: Improvement
> Components: runner-py-interactive
> Reporter: Ning Kang
> Assignee: Ning Kang
> Priority: P3
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The path length limit in Linux is 4096.
> The limit in windows API is 260.
> If long file name support is enabled in windows, the limit will be 32767.
> An example path that doesn't work on windows is
> c:\windows\temp\interactive-temp-xqj_fv471021776\cache-20-07-16-08_28_57\full\beam-temp-anonymous_pcollection_433934912-433934912-433938272-471021776-65e3a91ec73e11ea91b7e69191fc0bf0\284e0d91-ca8a-463c-a894-bde70cdec599.anonymous_pcollection_433934912-433934912-433938272-471021776
> (length: 281).
> Consider using obfuscation when mapping in-memory PCollections into files.
> If long file name is needed, consider storing a reverse indexed mapping in
> memory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
