SparkSQL UDTs with Ordering

[Patrick Woody <pa...@gmail.com>]

Hey all,

Currently looking into UDTs and I was wondering if it is reasonable to add
the ability to define an Ordering (or if this is possible, then how)?
Currently it will throw an error when non-Native types are used.

Thanks!
-Pat

Re: SparkSQL UDTs with Ordering

[Patrick Woody <pa...@gmail.com>]

Awesome. yep - I have seen the warnings on UDTs, happy to keep up with the
API changes :). Would this be a reasonable PR to toss up despite the API
unstableness or would you prefer it to wait?

Thanks
-Pat

On Tue, Mar 24, 2015 at 7:44 PM, Michael Armbrust <mi...@databricks.com>
wrote:

> I'll caution that the UDTs are not a stable public interface yet.  We'd
> like to do this someday, but currently this feature is mostly for MLlib as
> we have not finalized the API.
>
> Having an ordering could be useful, but I'll add that currently UDTs
> actually exist in serialized from so the ordering would have to be on the
> internal form, not the user visible form.
>
> On Tue, Mar 24, 2015 at 12:25 PM, Patrick Woody <pa...@gmail.com>
> wrote:
>
>> Hey all,
>>
>> Currently looking into UDTs and I was wondering if it is reasonable to
>> add the ability to define an Ordering (or if this is possible, then how)?
>> Currently it will throw an error when non-Native types are used.
>>
>> Thanks!
>> -Pat
>>
>
>

Re: SparkSQL UDTs with Ordering

[Michael Armbrust <mi...@databricks.com>]

I'll caution that the UDTs are not a stable public interface yet.  We'd
like to do this someday, but currently this feature is mostly for MLlib as
we have not finalized the API.

Having an ordering could be useful, but I'll add that currently UDTs
actually exist in serialized from so the ordering would have to be on the
internal form, not the user visible form.

On Tue, Mar 24, 2015 at 12:25 PM, Patrick Woody <pa...@gmail.com>
wrote:

> Hey all,
>
> Currently looking into UDTs and I was wondering if it is reasonable to add
> the ability to define an Ordering (or if this is possible, then how)?
> Currently it will throw an error when non-Native types are used.
>
> Thanks!
> -Pat
>