Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Refactor aggregation so we can register new functions easily without changing the engine #4

Closed
jvshahid opened this issue Oct 11, 2013 · 1 comment
Closed

Refactor aggregation so we can register new functions easily without changing the engine #4

jvshahid opened this issue Oct 11, 2013 · 1 comment
Milestone
v0.0.1

Comments

@jvshahid
Copy link
Contributor

No description provided.

@ghost ghost assigned jvshahid Oct 11, 2013
@jvshahid
Copy link
Contributor Author

Fixed in commit 4e6ce97

@jvshahid jvshahid removed their assignment Feb 24, 2015
@robinjha robinjha mentioned this issue Jul 23, 2015
Closed
@jhedlund jhedlund mentioned this issue Feb 23, 2016
Closed
This was referenced Feb 28, 2016
Closed
Closed
@pbooth pbooth mentioned this issue Mar 2, 2016
Closed
@pbooth pbooth mentioned this issue Oct 11, 2016
Closed
@zhu312542860 zhu312542860 mentioned this issue Jan 5, 2017
Closed
@ericb48 ericb48 mentioned this issue Apr 10, 2017
Closed
@rwrocket rwrocket mentioned this issue Jun 13, 2017
Closed
@itdevon itdevon mentioned this issue Jun 28, 2017
Closed
@rye rye mentioned this issue Jul 19, 2018
Closed
@ebb-tide ebb-tide mentioned this issue Dec 26, 2019
Closed
mgattozzi added a commit that referenced this issue Jun 3, 2024
@mgattozzi
feat: Create initial pro specific changes (#4)
93ac336 
This commit does a few things so show what working in the pro repo can
look like from a code perspective as well as minimizing code conflict
*between* pro and edge. It also sets us up to work on pro specific http
endpoints as well as setting up the skeleton of a compactor.

Neither of these changes does anythings particularly interesting. For
the pro http endpoint we just echo back what gets posted and for the
compactor we spawn a task that just sleeps in a continuous loop while
having access to the memory buffer and persister on startup. Overtime
the compactor can be expanded to work on actually compacting parquet
files and as for the pro endpoints we can add things as needed, such as
OAuth2 etc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v0.0.1
Development

No branches or pull requests
1 participant
@jvshahid