[
https://issues.apache.org/jira/browse/SYSTEMML-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533485#comment-15533485
]
Niketan Pansare commented on SYSTEMML-917:
------------------------------------------
1. Generate descriptive error message point to exact error instead of multiple
stack traces.
2. Line # and/or statement causing error from the script.
>> We follow the same principle in all our APIs and I think it would be a bad
>> idea to break it. Unless we decide to execute every single python invocation
>> and not push down anything (be it lazily or constrol structures), I think
>> this is something we will not fix in Python DSL itself. We can consider
>> improving the error throwing mechanism at Java side.
3. Explain to reflect HOPS etc properly.
>> Good point. I will create a subtask for it.
> Usability improvements for Python DSL
> -------------------------------------
>
> Key: SYSTEMML-917
> URL: https://issues.apache.org/jira/browse/SYSTEMML-917
> Project: SystemML
> Issue Type: Improvement
> Reporter: Arvind Surve
>
> Based on current experience of Python DSL, which we understand its in very
> early and experimental state, we need to have following addressed as a part
> of Python DSL support (assume similar will be applicable for Scala DSL)
> 1. Generate descriptive error message point to exact error instead of
> multiple stack traces.
> 2. Line # and/or statement causing error from the script.
> 3. Explain to reflect HOPS etc properly.
> Last time we observed that within a for loop it generates HOPS for every
> iteration, instead of once.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
