Hi Petr,
Could you please let me know if I am missing anything on the code as my
code is as same as snippet shared by you but still i am getting the below
error:
*error type mismatch: found String required: Serializable*
Please let me know if any fix to be applied on this
Regards,
Satish
Hi,
I am getting the below error while implementing the above custom class code
given by you
error type mismatch: found String required: Serializable
Please let me know if i am missing anything here
Regards,
Satish Chandra
On Wed, Sep 23, 2015 at 12:34 PM, Petr Novak
Thu, Sep 24, 2015 at 2:51 PM, Adrian Tanase <atan...@adobe.com> wrote:
>>
>>> +1 on grouping the case classes and creating a hierarchy – as long as
>>> you use the data programatically. For DataFrames / SQL the other ideas
>>> probably scale better…
>>
Cc: user
> Subject: Re: Scala Limitation - Case Class definition with more than 22
> arguments
>
> Can you switch to 2.11 ?
>
> The following has been fixed in 2.11:
> https://issues.scala-lang.org/browse/SI-7296
>
> Otherwise consider packaging related values into a case class
long as you
>> use the data programatically. For DataFrames / SQL the other ideas probably
>> scale better…
>>
>> From: Ted Yu
>> Date: Wednesday, September 23, 2015 at 7:07 AM
>> To: satish chandra j
>> Cc: user
>> Subject: Re: Scala Limitation - Cas
Class definition with more than 22
arguments
Can you switch to 2.11 ?
The following has been fixed in 2.11:
https://issues.scala-lang.org/browse/SI-7296
Otherwise consider packaging related values into a case class of their own.
On Tue, Sep 22, 2015 at 8:48 PM, satish chandra j
<jsatishc
You can implement your own case class supporting more then 22 fields. It is
something like:
class MyRecord(val val1: String, val val2: String, ... more then 22,
in this case f.e. 26)
extends Product with Serializable {
def canEqual(that: Any): Boolean = that.isInstanceOf[MyRecord]
def
If you need to understand what is the magic Product then google up
Algebraic Data Types and learn it together with what is Sum type. One
option is http://www.stephanboyer.com/post/18/algebraic-data-types
Enjoy,
Petr
On Wed, Sep 23, 2015 at 9:07 AM, Petr Novak wrote:
> I'm
HI Andy,
So I believe if I opt pro grammatically building the schema approach, than
it would not have have any restriction as such in "case Class not allowing
more than 22 Arguments"
As I need to define a schema of around 37 arguments
Regards,
Satish Chandra
On Wed, Sep 23, 2015 at 9:50 AM,
Yes and I would recommend it because it can be made generic and reusable
too
On Wed, Sep 23, 2015 at 5:37 PM, satish chandra j
wrote:
> HI Andy,
> So I believe if I opt pro grammatically building the schema approach, than
> it would not have have any restriction as
HI All,
Do we have any alternative solutions in Scala to avoid limitation in
defining a Case Class having more than 22 arguments
We are using Scala version 2.10.2, currently I need to define a case class
with 37 arguments but getting an error as "*error: Implementation
restriction: case classes
Alternatively, I would suggest you looking at programmatically building the
schema
refer to
http://spark.apache.org/docs/latest/sql-programming-guide.html#programmatically-specifying-the-schema
Cheers
Andy
On Wed, Sep 23, 2015 at 2:07 PM, Ted Yu wrote:
> Can you switch to
Can you switch to 2.11 ?
The following has been fixed in 2.11:
https://issues.scala-lang.org/browse/SI-7296
Otherwise consider packaging related values into a case class of their own.
On Tue, Sep 22, 2015 at 8:48 PM, satish chandra j
wrote:
> HI All,
> Do we have any
13 matches
Mail list logo