# Using Node-RED to transfer data from InfluxDB 1.7 to 2.3, but receiving ENOBUFS error when dataset is too large

**URL:** <https://discourse.nodered.org/t/using-node-red-to-transfer-data-from-influxdb-1-7-to-2-3-but-receiving-enobufs-error-when-dataset-is-too-large/65532>\
**Category:** General\
**Created:** [24 July 2022 14:19 UTC](https://discourse.nodered.org/t/using-node-red-to-transfer-data-from-influxdb-1-7-to-2-3-but-receiving-enobufs-error-when-dataset-is-too-large/65532 "2022-07-24T14:19:48Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![grant1](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/grant1/32/49890_2.png) [@grant1](https://discourse.nodered.org/u/grant1)\
**Post date:** [24 July 2022 23:52 UTC](https://discourse.nodered.org/t/using-node-red-to-transfer-data-from-influxdb-1-7-to-2-3-but-receiving-enobufs-error-when-dataset-is-too-large/65532/9 "2022-07-24T23:52:33Z")

</div>

Thank you @Colin. I needed some more time to think about this, and I got it all working well using a single function node containing this:

```auto
msg.payload = msg.payload.map(function(value) {
    return {
        measurement: "SingleRotaryFurnaceZoneData",
        fields: {
            temperature:value.last,
        },
        tags:{
            MeasType:"actual",
            EquipNumber:"1",
            EquipZone:"zone1"
        },
        timestamp: value.time
    };
});
return msg;

```

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/0/600f5c73031413da1ee22392c254139e8a1b46f2.png)

An array with 378,000 objects (about 9.5 months of data, with 1 reading per minute) took \< 10 seconds to import into Influx 2.3 using the batch node.

---

_[View the full topic](https://discourse.nodered.org/t/using-node-red-to-transfer-data-from-influxdb-1-7-to-2-3-but-receiving-enobufs-error-when-dataset-is-too-large/65532)._