Re: Adding/Using More Resolution Types on JIRA

2015-05-21 22:39 GMT+02:00 Sean Owen : > > I don't think sorting helps or that browsing is the issue. What if > you're searching for Open Critical issues concerning Pyspark? If the > list is full of issues that are actually out of scope, later, won't > fix, then that's a problem. Sure. That is why

Re: Adding/Using More Resolution Types on JIRA

Some examples to illustrate my point. A couple of issues from the oldest open issues in the SQL component: [SQL] spark-sql exits while encountered an error https://issues.apache.org/jira/browse/SPARK-4572 This is an incomplete report that nobody can take action on. It can be resolved as "Incomplet

Re: Adding/Using More Resolution Types on JIRA

2015-05-12 9:50 GMT+02:00 Patrick Wendell : > > Inactive - A feature or bug that has had no activity from users or > developers in a long time > Why is this needed? Every JIRA listing can be sorted by activity. That gets the inactive ones out of your view quickly. I do not see any reason why an i

Simple SQL queries producing invalid results [SPARK-6743]

Hi, Could someone give a look to this issue? [SPARK-6743] Join with empty projection on one side produces invalid results https://issues.apache.org/jira/browse/SPARK-6743 Thank you, -- Santiago M. Mola Vía de las dos Castillas, 33, Ática 4, 3ª Planta 28224 Pozuelo d