hashmapinc / hashmapinc/Drillflow

DEV:LOG: Really need to throw a -1 if Channels/Data Fails During an AddToStore

Open
#605 3 comments 0 reactions 1 assignee Claimed by @TessForGithub2 View on GitHub
API bug
Dominant language
Java
Stars
21
Forks
13
PR merge metrics
No merged PRs in 30d

Description

Refer to ticket #603.

I commented out the failure of DoT returning a 500 (Internal Server Error) in spite of creating a log with 100% fidelity when queried after the AddToStore.

There are two DoT errors here:
1. Why does DoT return a 500 when a subsequent query of the Add shows 100% fidelity (the data that caused the 500 was successfully added & subsequently returned by DoT during a query)?

I will check against the DoT API to see that I get the same behavior. However, at this point in time, it appears to be a DoT error.

2. Per an email dated March 21 from Jingjing Wang "New API changes for ChannelSet APIs", he states:

"4) if step 2 or 3 failed, you do not need roll back previous step, you can retry step 2 or 3, we will merge the channels or overwrite channel data at this scenario. And once you delete ChannelSet, all related channel and data will be deleted."

So our understanding is that, on a Client side retry, all will work as expected; however, we will receive a -409 (UUID already exists). I will verify this again, but if this is true (-409), then this again is a DoT error.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.