Github user HarshSharma8 commented on the issue:
https://github.com/apache/spark/pull/16997
Hello Sean,
I apologize for bold instead of back-ticks, and i'm updating the content
for this.
Thank You
Best Regards |
*Harsh Sharma*
Sr. Software Consultant
Facebook <https://www.facebook.com/harsh.sharma.161446> | Twitter
<https://twitter.com/harsh_sharma5> | Linked In
<https://www.linkedin.com/in/harsh-sharma-0a08a1b0?trk=hp-identity-name>
[email protected]
Skype*: khandal60*
*+91-8447307237*
On Tue, Feb 21, 2017 at 10:58 AM, Sean Owen <[email protected]>
wrote:
> *@srowen* commented on this pull request.
> ------------------------------
>
> In docs/sql-programming-guide.md
> <https://github.com/apache/spark/pull/16997#discussion_r102134397>:
>
> > @@ -297,6 +297,9 @@ reflection and become the names of the columns.
Case classes can also be nested
> types such as `Seq`s or `Array`s. This RDD can be implicitly converted
to a DataFrame and then be
> registered as a table. Tables can be used in subsequent SQL statements.
>
> +Spark Encoders are used to convert a JVM object to Spark SQL
representation. To create dataset, spark requires an encoder which takes the
form of <b>Encoder[T]</b> where <b>T</b> is the type which has to be encoded.
Creation of a dataset with a custom type of object, may result into
<b>java.lang.UnsupportedOperationException: No Encoder found for
Object-Name</b>.
>
> Yes, @HarshSharma8 <https://github.com/HarshSharma8> this still doesn't
> address the comments. Use back-ticks for code, not bold, too. What is
> Object-Name?
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/16997#discussion_r102134397>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AKIiQM8Tsz96c1KHGszvbFmgJnnRD62Gks5renYPgaJpZM4MF0vf>
> .
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
