Hi, So, since ML component's invoke Spark, if there's a SparkException, ML component should log it properly. And if you need to see an internal Spark error, you have to correlate them using the timestamp. Will it be sufficient?
On Mon, Jun 8, 2015 at 12:38 PM, Maheshakya Wijewardena <mahesha...@wso2.com > wrote: > +1 > It sure is cluttering things up. > > But wont there be an inconvenience when we need to relate some issue in a > carbon component with the actual spark issue? > > On Mon, Jun 8, 2015 at 12:24 PM, Niranda Perera <nira...@wso2.com> wrote: > >> +1 for this. >> >> Even in DAS this is an issue & think this would be a better option >> >> >> On Mon, Jun 8, 2015 at 12:22 PM, Nirmal Fernando <nir...@wso2.com> wrote: >> >>> All, >>> >>> What do you think about https://wso2.org/jira/browse/ML-68 ? >>> >>> Reason: >>> >>> Spark logs are cluttering the wso2carbon.log and it'll be convenient to >>> have the spark logs in a different file. >>> >>> -- >>> >>> Thanks & regards, >>> Nirmal >>> >>> Associate Technical Lead - Data Technologies Team, WSO2 Inc. >>> Mobile: +94715779733 >>> Blog: http://nirmalfdo.blogspot.com/ >>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Niranda Perera* >> Software Engineer, WSO2 Inc. >> Mobile: +94-71-554-8430 >> Twitter: @n1r44 <https://twitter.com/N1R44> >> https://pythagoreanscript.wordpress.com/ >> > > > > -- > Pruthuvi Maheshakya Wijewardena > Software Engineer > WSO2 Lanka (Pvt) Ltd > Email: mahesha...@wso2.com > Mobile: +94711228855 > > > -- Thanks & regards, Nirmal Associate Technical Lead - Data Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
