You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Balu Vellanki (JIRA)" <ji...@apache.org> on 2016/01/04 22:22:39 UTC

[jira] [Commented] (FALCON-1712) Falcon operations not happening if entity name is longer than 255 characters.

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

Balu Vellanki commented on FALCON-1712:
---------------------------------------

[~deepak.barr]  and [~pallavi.rao] : Sorry if I missed past emails (catching up after vacation). All entity XSD in Falcon limit name of entity to 40 chars.
{code}
<xs:simpleType name="IDENTIFIER">
        <xs:restriction base="xs:string">
            <xs:pattern value="(([a-zA-Z]([\-a-zA-Z0-9])*){1,39})"/>
        </xs:restriction>
    </xs:simpleType>
{code}

So this should never be an issue. Is our XSD based entity validation working properly?

> Falcon operations not happening if entity name is longer than 255 characters.
> -----------------------------------------------------------------------------
>
>                 Key: FALCON-1712
>                 URL: https://issues.apache.org/jira/browse/FALCON-1712
>             Project: Falcon
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 0.9
>            Reporter: Pragya Mittal
>            Assignee: Deepak Barr
>         Attachments: mysql_stacktrace
>
>
> Entity operations for id greater than 255 characters  shows inconsistent result with following error in logs :
> {noformat}
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Data truncation: Data too long for column 'id' at row 1 {prepstmnt 1461009657 INSERT INTO INSTANCES (id, actual_end_time, actual_start_time, awaited_predicates, cluster, creation_time, current_state, entity_id, external_id, instance_sequence, instance_time, properties, ENTITYBEAN_ID) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)} [code=1406, state=22001]
> 	at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:218)
> 	at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:194)
> 	at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:58)
> 	at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:1133)
> 	at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:275)
> 	at org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1791)
> 	at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:268)
> 	at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:119)
> {noformat}



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