You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/09/03 17:07:01 UTC
[jira] [Commented] (BEAM-10514) Make sure Interactive Beam cache
file path length does not exceed OS limits
[ https://issues.apache.org/jira/browse/BEAM-10514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190306#comment-17190306 ]
Beam JIRA Bot commented on BEAM-10514:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.
> 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
> Labels: stale-assigned
> 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)