Brick-server Issues

[Jimmy Li]

Hey guys,

I'm just asking, is the brick server still under maintenance?

[Jason Koh]

Hi Jimmy,

I have been away from maintaining that for a while due to my day job and personal events. I will try to find some time for resolving the issues in this week.

That said, I don't have enough cycles to actively develop the code outside intermittently reviewing PRs and Issues. I'd be happy to guide any voluntary developer/maintainer though.

With regards,

Jason Koh
jbkoh.github.io

On Thu, Jul 22, 2021 at 6:19 AM Jimmy Li <campho...@gmail.com> wrote:

Hey guys,

I'm just asking, is the brick server still under maintenance?

--
You received this message because you are subscribed to the Google Groups "Brick User Forum (Unified Building Metadata Schema)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brickschema...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/brickschema/eedc885f-3b3d-4b7f-86a8-fa59db967714n%40googlegroups.com.

[Jason Koh]

Btw, what's your major use case of brick-server? Do you plan to use the API for developing your application or try to learn the concepts of how to use Brick with timeseries data? If it's the latter case, Gabe's recent tutorial over using Brick with TimescaleDB is a great alternative too: https://www.youtube.com/watch?v=kZYNXoiM8gk

With regards,

Jason Koh
jbkoh.github.io

[Jimmy Li]

Thanks, I found the causes. The wrong order of timestamps caused 500. Timescaledb exited with code 1 was caused by not enough disk space.

But it would be great to have a guide on how to create the postgresql image. 

Gabe's video is also an option.

[Jason Koh]

Hey Jimmy, glad you figured it out. I will add a lint layer in the code to capture that. The disk space issue was unknown to me. Will check if timescale has some general guidance for it.

To view this discussion on the web visit https://groups.google.com/d/msgid/brickschema/b03c6153-90d1-4b3b-b0ee-62a187d33b6dn%40googlegroups.com.

[Gabe Fierro]

Hi everyone:

TimescaleDB has support for retention policies which can drop older data when requested. You may also want to look into compression which has been very effective for reducing disk space in my experience.

Best,

Gabe

To view this discussion on the web visit https://groups.google.com/d/msgid/brickschema/CAJfunc2CBna9OR7uT1q3_f%2BEUvjFb6OGnV9AevMgfmTjT4QnZw%40mail.gmail.com.