[
https://issues.apache.org/jira/browse/PHOENIX-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000913#comment-15000913
]
Gabriel Reid commented on PHOENIX-2387:
---------------------------------------
{quote}Use sandbox for dev environment only - where you're building the code
and want an easy way to try out something. It works in this regard currently,
yes?{quote}
Yes, this works fine right now (and it's the use case that I currently have).
{quote}Release a docker image with our binary releases to make this easy for
our users (and explicitly don't include the sandbox.py script in our binary
distributions so as not to confuse users).{quote}
That sounds good to me. I'll leave this a little longer to see if anyone has
any thoughts either way, but in the absence of any other strong opinions on
this, I'll update the binary release build to omit the sandbox script.
> 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)
