[
https://issues.apache.org/jira/browse/PHOENIX-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995411#comment-14995411
]
Gabriel Reid commented on PHOENIX-2387:
---------------------------------------
[~jmahonin] ok, I just clued in to the fact that this was an issue with the
binary release (right?). In that case, no, the root cause isn't fixed. The
error message that wasn't getting properly printed tells the user that the
maven build needs to be re-run (to create the "cached_classpath.txt" file), but
of course that won't help much with a binary release.
I'll re-open this and make a fix that works for the binary release as well.
> Phoenix sandbox doesn't launch
> ------------------------------
>
> Key: PHOENIX-2387
> URL: https://issues.apache.org/jira/browse/PHOENIX-2387
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.6.0
> Reporter: Josh Mahonin
> Assignee: Gabriel Reid
> Priority: Minor
> Fix For: 4.7.0
>
> Attachments: PHOENIX-2387.patch
>
>
> Just tried the stock 4.6.0 download to try check a user issue and ran the
> sandbox. This was the output:
> ./phoenix_sandbox.py
> Traceback (most recent call last):
> File "./phoenix_sandbox.py", line 36, in <module>
> sys.err.write("cached_classpath.txt is not present under "
> AttributeError: 'module' object has no attribute 'err'
> There's no 'cached_classpath.txt' file in the folder
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
