---
sort_order: 113
tei_id: rdx_191dd.p.idp18666864
annotation_count: 0
images:
small-thumbnail: https://readux.ecds.emory.edu/books/emory:191dd/pages/emory:rfh06/mini-thumbnail/
json: https://readux.ecds.emory.edu/books/emory:191dd/pages/emory:rfh06/info/
full: https://readux.ecds.emory.edu/books/emory:191dd/pages/emory:rfh06/fs/
page: https://readux.ecds.emory.edu/books/emory:191dd/pages/emory:rfh06/single-page/
thumbnail: https://readux.ecds.emory.edu/books/emory:191dd/pages/emory:rfh06/thumbnail/
title: Page 113
number: 113
---
{% raw %}Bm deminq carleton. 115{% endraw %}
{% raw %}" Pardon this mtrusion. Miss Newcome; I beg your pardon,{% endraw %}
{% raw %}Mr. Allen—that is your name, I believe—but my errand av as{% endraw %}
{% raw %}one that reqiured dispatch. Mr. Mauvais will tell you the{% endraw %}
{% raw %}business I have come about—simply to take the guardianship{% endraw %}
{% raw %}of this young lady away from him. What does my niece say{% endraw %}
{% raw %}to taking her uncle for guardian ?" said the stranger, advanc¬{% endraw %}
{% raw %}ing to Alicia and clasping her hand.{% endraw %}
{% raw %}"WeU, I do declare!" murmured Mrs. Wyman, who,{% endraw %}
{% raw %}hearing strange voices, came in with a lamp.{% endraw %}
{% raw %}" How do you do, madam ? You have not forgotten me, I{% endraw %}
{% raw %}see. I appear and disappear in very mysterious ways, for{% endraw %}
{% raw %}which I have to ask your pardon. But, as this niece of mine{% endraw %}
{% raw %}says, one sometimes has motives not apparent to every{% endraw %}
{% raw %}one—ha! ha!"{% endraw %}
{% raw %}" Take seats, gentlemen," said Mrs. Wyman, to her visitors.{% endraw %}
{% raw %}" I don't know your name, sir, but I am very glad to see you,{% endraw %}
{% raw %}if you are a friend of Alicia's."{% endraw %}
{% raw %}" My name is Carleton, madam—Sir Deming Carletan, at{% endraw %}
{% raw %}home—Mr. Carieton, in the United States, I suppose. Thank{% endraw %}
{% raw %}you, I will take a seat."{% endraw %}
{% raw %}" Good-evening," said AUen, in the doorway.{% endraw %}
{% raw %}" No, I beg your pardon, I am not ready to say good-{% endraw %}
{% raw %}evening to you yet, Mr. Allen," Sir Deming said, hastily,{% endraw %}
{% raw %}rising and bowing to the young man. " Pray remain, sir;{% endraw %}
{% raw %}you need have no fears of intruding where your companv is{% endraw %}
{% raw %}so desirable," he added, glancing at Alicia, close to whose side{% endraw %}
{% raw %}he had drawn a chair. " Now, Mr. Mauvais," continued Sir{% endraw %}
{% raw %}Deming, when Alien was seated, " please tell this youug lady{% endraw %}
{% raw %}the errand we came upon."{% endraw %}
{% raw %}" This gentleman," said the Frenchman, addressiug himself{% endraw %}
{% raw %}to Ahcia, " has been able to convice me, however reluctantly,{% endraw %}
{% raw %}that his right to the guardianship of your fair self is better{% endraw %}
{% raw %}founded than my own. At all events, it is based on a legal{% endraw %}
{% raw %}claim, while mine is not. He is undoubtedly your uncle, on{% endraw %}
{% raw %}your mother's side, and is able to do for you aU -w'hich it{% endraw %}
{% raw %}would have been my highest pleasure to have done. There¬{% endraw %}
{% raw %}fore, I resign you into his hands. I have already prepared{% endraw %}
{% raw %}him to find in you aU that is lovely and endearing, and I{% endraw %}
{% raw %}Xish you, dear Miss AUcia, all 'ihe happiness you so eminently{% endraw %}
{% raw %}deserve."{% endraw %}


New Record State Extraction
|
This single message transformation (SMT) is supported for only the SQL database connectors. For the MongoDB connector, see the documentation for the MongoDB equivalent to this SMT. |
A Debezium data change event has a complex structure that provides a wealth of information. Kafka records that convey Debezium change events contain all of this information. However, parts of a Kafka ecosystem might expect Kafka records that provide a flat structure of field names and values. To provide this kind of record, Debezium provides the event flattening single message transformation (SMT). Configure this transformation when consumers need Kafka records that have a format that is simpler than Kafka records that contain Debezium change events.
The event flattening transformation is a Kafka Connect SMT.
Change event structure
Debezium generates data change events that have a complex structure. Each event consists of three parts:
-
Metadata, which includes but is not limited to:
-
The operation that made the change
-
Source information such as the names of the database and table where the change was made
-
Time stamp for when the change was made
-
Optional transaction information
-
-
Row data before the change
-
Row data after the change
For example, part of the structure of an UPDATE
change event looks like this:
{
"op": "u",
"source": {
...
},
"ts_ms" : "...",
"before" : {
"field1" : "oldvalue1",
"field2" : "oldvalue2"
},
"after" : {
"field1" : "newvalue1",
"field2" : "newvalue2"
}
}
More details about change event structure are provided in the documentation for each connector.
This complex format provides the most information about changes happening in the system. However, other connectors or other parts of the Kafka ecosystem usually expect the data in a simple format like this:
{
"field1" : "newvalue1",
"field2" : "newvalue2"
}
To provide the needed Kafka record format for consumers, configure the event flattening SMT.
Behavior
The event flattening SMT extracts the after
field from a Debezium change event in a Kafka record. The SMT replaces the original change event with only its after
field to create a simple Kafka record.
You can configure the event flattening SMT for a Debezium connector or for a sink connector that consumes messages emitted by a Debezium connector. The advantage of configuring event flattening for a sink connector is that records stored in Apache Kafka contain whole Debezium change events. The decision to apply the SMT to a source or sink connector depends on your particular use case.
You can configure the transformation to do any of the following:
-
Add metadata from the change event to the simplified Kafka record. The default behavior is that the SMT does not add metadata.
-
Keep Kafka records that contain change events for
DELETE
operations in the stream. The default behavior is that the SMT drops Kafka records forDELETE
operation change events because most consumers cannot yet handle them.
A database DELETE
operation causes Debezium to generate two Kafka records:
-
A record that contains
"op": "d",
thebefore
row data, and some other fields. -
A tombstone record that has the same key as the deleted row and a value of
null
. This record is a marker for Apache Kafka. It indicates that log compaction can remove all records that have this key.
Instead of dropping the record that contains the before
row data, you can configure the event flattening SMT to do one of the following:
-
Keep the record in the stream and edit it to have only the
"value": "null"
field. -
Keep the record in the stream and edit it to have a
value
field that contains the key/value pairs that were in thebefore
field with an added"__deleted": "true"
entry.
Similary, instead of dropping the tombstone record, you can configure the event flattening SMT to keep the tombstone record in the stream.
Configuration
Configure the Debezium event flattening SMT in a Kafka Connect source or sink connector by adding the SMT configuration details to your connector’s configuration. To obtain the default behavior, in a .properties
file, you would specify something like the following:
transforms=unwrap,...
transforms.unwrap.type=io.debezium.transforms.ExtractNewRecordState
As for any Kafka Connect connector configuration, you can set transforms=
to multiple, comma-separated, SMT aliases in the order in which you want Kafka Connect to apply the SMTs.
The following .properties
example sets several event flattening SMT options:
transforms=unwrap,...
transforms.unwrap.type=io.debezium.transforms.ExtractNewRecordState
transforms.unwrap.drop.tombstones=false
transforms.unwrap.delete.handling.mode=rewrite
transforms.unwrap.add.fields=table,lsn
drop.tombstones=false
-
Keeps tombstone records for
DELETE
operations in the event stream. delete.handling.mode=rewrite
-
For
DELETE
operations, edits the Kafka record by flattening thevalue
field that was in the change event. Thevalue
field directly contains the key/value pairs that were in thebefore
field. The SMT adds__deleted
and sets it totrue
, for example:"value": { "pk": 2, "cola": null, "__deleted": "true" }
add.fields=table,lsn
-
Adds change event metadata for the
table
andlsn
fields to the simplified Kafka record.
Adding metadata
The event flattening SMT can add original, change event metadata to the simplified Kafka record. For example, you might want the simplified record’s header or value to contain any of the following:
-
The type of operation that made the change
-
The name of the database or table that was changed
-
Connector-specific fields such as the Postgres LSN field
For more information on what is available see the documentation for each connector.
To add metadata to the simplified Kafka record’s header, specify the add.header
option.
To add metadata to the simplified Kafka record’s value, specify the add.fields
option.
Each of these options takes a comma separated list of change event field names. Do not specify spaces. When there are duplicate field names, to add metadata for one of those fields, specify the struct as well as the field. For example:
transforms=unwrap,... transforms.unwrap.type=io.debezium.transforms.ExtractNewRecordState transforms.unwrap.add.fields=op,table,lsn,source.ts_ms transforms.unwrap.add.headers=db transforms.unwrap.delete.handling.mode=rewrite
With that configuration, a simplified Kafka record would contain something like the following:
{
...
"__op" : "c",
"__table": "MY_TABLE",
"__lsn": "123456789",
"__source_ts_ms" : "123456789",
...
}
Also, simplified Kafka records would have a __db
header.
In the simplified Kafka record, the SMT prefixes the metadata field names with a double underscore. When you specify a struct, the SMT also inserts an underscore between the struct name and the field name.
To add metadata to a simplified Kafka record that is for a DELETE
operation, you must also configure delete.handling.mode=rewrite
.
Configuration options
The following table describes the options that you can specify to configure the event flattening SMT.
| Option | Default | Description |
|---|---|---|
|
Debezium generates a tombstone record for each |
|
|
Debezium generates a change event record for each |
|
To use row data to determine the topic to route the record to, set this option to an |
||
__ (double-underscore) |
Set this optional string to prefix a field. |
|
Set this option to a comma-separated list, with no spaces, of metadata fields to add to the simplified Kafka record’s value. When there are duplicate field names, to add metadata for one of those fields, specify the struct as well as the field, for example |
||
__ (double-underscore) |
Set this optional string to prefix a header. |
|
Set this option to a comma-separated list, with no spaces, of metadata fields to add to the header of the simplified Kafka record. When there are duplicate field names, to add metadata for one of those fields, specify the struct as well as the field, for example |


It's a discord bot that can give you the color palette of images, you can use the commands with the prefix "+"
What it does?
Gives you the color palette of an image
-Reply to a message containing a image with the command "+getcolor","+color" or "+colors" and if you want more colors just reply to the answer with "+more"
It can give you the name of an color
-Use the command "+name (hex)" example: "+name #FF0000"


The BottomSheet are views that come up from the bottom of the screen, elevated over the main content. This UX pattern is intended for mobile devices only.
class="mat-button-raised color-primary open-bs" data-bottomsheet="BSmenu1"
class="mat-button-raised color-primary open-bs" data-bottomsheet="BSmenu1"
class="mat-button-raised color-primary open-bs" data-bottomsheet="BSmenu1"