[jira] [Commented] (EAGLE-687) When creating sites in UI and metadata storaged as jdbc, the field "Description" can't be null

["Jayesh (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/EAGLE-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781811#comment-15781811 ] 

Jayesh commented on EAGLE-687:
------------------------------

[~chitin], after reviewing the code responsible for this, i see much bigger issue at how SiteEntityToRelation class is designed. so right now the issue is about not able to set null description, but later it might cause similar issues for other fields ( specially when new queries are introduced )
proposed solution:
SiteEntityToRelation.accept method should take variable argument instead of siteEntity, that way it can be controlled well at a time of creating query using queryService.




> When creating sites in UI and metadata storaged as jdbc, the field "Description"  can't be null
> -----------------------------------------------------------------------------------------------
>
>                 Key: EAGLE-687
>                 URL: https://issues.apache.org/jira/browse/EAGLE-687
>             Project: Eagle
>          Issue Type: Bug
>            Reporter: Lingang Deng
>            Priority: Minor
>             Fix For: v0.5.0
>
>
> When creating sites in UI and metadata storaged as jdbc, the field "Description"  can't be null, or we will get error
> {code}
> ERROR [2016-10-26 15:54:24,554] org.apache.eagle.metadata.store.jdbc.JDBCMetadataMetadataStoreServiceImpl: Error to insert batch: INSERT INTO sites (siteid, sitename, description, createdtime, modifiedtime, uuid) VALUES (?, ?, ?, ?, ?, ?)
> ! java.sql.SQLException: No value specified for parameter 6
> {code}
> The  filed "Description" is checked in the background. So whether this field can be empty or validated in the front end , it's elective.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)