Message-ID: <812277330.8636.1711716058259.JavaMail.confluence@ip-172-30-4-17.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8635_382308414.1711716058255" ------=_Part_8635_382308414.1711716058255 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html get_dirty_state

get_dirty_state

The get_dirty_state message is sent to get stat= e information about the need to synchronize with a dimension table.

=20

Get Dimension Synchronize State Informati= on

=20

To get dirty state information, the sequence of events is as follows:

=20
    =20
  1. The client specifies a request to obtain the dirty state information=20
  2. The ontology server returns the dirty state information
  3. =20
=20



= =20

get_dirty_state Request Message

=20

This message has no requirements or attributes settings.
Example:
<message_body>
<get_dirty_state/>
<= ;/message_body>
=

=20

get_dirty_state Response Message

=20

A status type of DONE or ERROR is spe= cified in the response header. The <message_body> provides t= he dirty state information.
E= xample:
<message= _body>
<>NONE|AD= D|DELETE_EDIT</dirty_state>
</message_body>

The following dirty_state codes a= re in use:

=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20

dirty_state code

Description

NONE

Indicates that no synchronization or update a= ctions are required

ADD

Indicates an update action is required

=20

DELETE_EDIT

Indicates a synchronization action is require= d

=20



------=_Part_8635_382308414.1711716058255--