}

func saveKeyEtcd(ctx context.Context, client *etcd.Client, key string, data []byte, opts ...options) error {
	timeoutCtx, cancel := context.WithTimeout(ctx, defaultContextTimeout)
	defer cancel()
	if len(opts) > 0 {
		return saveKeyEtcdWithTTL(ctx, client, key, data, opts[0].ttl)
	}
	_, err := client.Put(timeoutCtx, key, string(data))
	etcdLogIf(ctx, err)
	return etcdErrToErr(err, client.Endpoints())
}

  -u admin:admin \
  --data-binary @documents.ndjson
```

#### Crawl-Based Migration

Alternatively, let Fess recrawl your content:

1. **Web Content**: Configure Web Crawler with starting URLs
2. **File Shares**: Configure File Crawler with SMB/FTP paths
3. **Databases**: Configure Data Store crawling with JDBC connections

---

## Data Import Methods

                                            <c:forEach var="data" varStatus="s"
                                                       items="${duplicateHostItems}">
                                                <tr
                                                        data-href="${contextPath}/admin/duplicatehost/details/4/${f:u(data.id)}" role="button" tabindex="0">

    send(function(err, data) {
        if (err) {
            console.log("Error", err);
        } else {
            console.log("Success", data);
        }
    });


// Download a file in the archive and store it in /tmp/data.csv
var file = require('fs').createWriteStream('/tmp/data.csv');
s3.getObject({Bucket: 'your-bucket', Key: 'path/to/file.zip/data.csv'}).

```
rm -rf /tmp/etcd-data.tmp && mkdir -p /tmp/etcd-data.tmp && \
  podman rmi gcr.io/etcd-development/etcd:v3.3.9 || true && \
  podman run \
  -p 2379:2379 \
  -p 2380:2380 \
  --mount type=bind,source=/tmp/etcd-data.tmp,destination=/etcd-data \
  --name etcd-gcr-v3.3.9 \
  gcr.io/etcd-development/etcd:v3.3.9 \
  /usr/local/bin/etcd \
  --name s1 \
  --data-dir /etcd-data \
  --listen-client-urls http://0.0.0.0:2379 \

                        .status(ApiResult.Status.OK)
                        .result());
    }

    /**
     * Retrieves a specific data config setting by ID.
     *
     * @param id the ID of the data config to retrieve
     * @return JSON response containing the data config setting
     */
    // GET /api/admin/dataconfig/setting/{id}
    @Execute
    public JsonResponse<ApiResult> get$setting(final String id) {

                                                                name="deleteAllWords"
                                                                data-toggle="modal" data-target="#confirmToAllDelete"
                                                                value="<la:message key="labels.design_delete_button" />">

d-with-errors":"disabled-without-errors").on("reset",function(){e(a(this),"disabled")}).find("*[data-validation]").valAttr("event","keyup change").on("validation",function(b,c){if(!f){f=!0;var g=a(this).closest("form");c&&d(g,this,h)?e(g,"enabled"):e(g,"disabled"),f=!1}}).on("afterValidation",k).on("blur",function(){a(this).valAttr("have-been-blurred",1)}).each(function(){var b=a(this),c=b.attr("data-validation");c.indexOf("checkbox_group")>-1&&b.closest("form").find('input[name="'+b.attr("name"...

- **Size of Serialized Data:**
Java serialization tends to produce larger serialized objects because it includes class metadata and other overhead.

- **Flexibility and Control:**
Java serialization offers limited control over the serialization process, such as excluding certain fields, customizing naming conventions, and handling complex data structures more gracefully.

- **Security:**

// it will be called for input validation failures
func Fatal(err error, msg string, data ...any) {
	fatal(err, msg, data...)
}

func fatal(err error, msg string, data ...any) {
	if msg == "" {
		if len(data) > 0 {
			msg = fmt.Sprint(data...)
		} else {
			msg = "a fatal error"
		}
	} else {
		msg = fmt.Sprintf(msg, data...)
	}
	consoleLog(fatalMessage, errorFmtFunc(msg, err, jsonFlag))
}