Skip to content

Conversation

@nikhilsinhaparseable
Copy link
Contributor

in PUT /logstream/{logstream}/hottier
request body:

{ "size": "10737418240" }
the size is expected to be in bytes

GET /logstream/{logstream}/hottier
response body:
{
"size": "1073741824",
"used_size": "121798121",
"available_size": "951943703",
"oldest_date_time_entry": "2024-08-10 11:45:00"
}

size, used_size, available_size are sent in bytes

@balaji-jr
Copy link
Contributor

balaji-jr commented Aug 10, 2024

Can we add the " bytes" as a suffix to all the sizes?
Also timezone info on the 'oldest_date_time_entry'

Copy link
Member

@nitisht nitisht left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we discussed let's make it in sync with other API, i.e.

  • Add the " bytes" as a suffix to all the sizes e.g. 123324354 Bytes
  • Timezone info on the 'oldest_date_time_entry' e.g. 2011-08-12T20:17:46.384Z

@nikhilsinhaparseable nikhilsinhaparseable force-pushed the hot-tier-size-bytes branch 2 times, most recently from feff8dd to c6bbf12 Compare August 13, 2024 12:34
in PUT /logstream/{logstream}/hottier
request body:

`
{
    "size": "10737418240"
}
`
the size is expected to be in bytes

GET /logstream/{logstream}/hottier
response body:
{
    "size": "1073741824 Bytes",
    "used_size": "121798121 Bytes",
    "available_size": "951943703 Bytes",
    "oldest_date_time_entry": "2024-08-10T11:45:00.000Z"
}

size, used_size, available_size are sent in bytes
suffixed "Bytes" to size, available_size and  used_size
@nitisht nitisht merged commit 900bf47 into parseablehq:main Aug 15, 2024
@nikhilsinhaparseable nikhilsinhaparseable deleted the hot-tier-size-bytes branch July 12, 2025 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants