You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by "uuf6429 (via GitHub)" <gi...@apache.org> on 2023/02/09 18:50:47 UTC
[GitHub] [druid] uuf6429 opened a new issue, #13784: Usability problems
uuf6429 opened a new issue, #13784:
URL: https://github.com/apache/druid/issues/13784
I'm completely new to Druid and I'm evaluating it as a DW+Analytics solution (using the docker-compose sample from this repo).
Unfortunately, I've had some problems working with it. I think some of them might be intentional, but maybe not so clear to a first time user? Here goes:
1. If data is not loaded successfully after ingestion (e.g. records do not match the preconfigured task regex), the _ingestion itself is marked as successful_, but _nothing is imported_. To me this is a problem for these reasons:
a. this effectively means data might be / is being lost
b. this is happening without warning
c. couldn't find any logging related to this (the logs panel was not useful tracking this problem)
2. When I had two ingestion tasks pointing to the same datasource, the last one ended up overwriting data from the previous one. I still can't figure out the exact reason, but:
a. as a data platform, data should be sacred 😄 - it should triple check with the user if data is overwritten or dropped automatically
b. while investigating, I came up to the "segment granularity" setting, which is I assume relates to my problem - again, if it is potentially removing data, it should be visually prominent
c. in my opinion, the UX should be geared to a more cautious approach - ie, it's easier to delete data than getting it back, so maybe it's better to have defaults that ensure data is retained
3. Not sure if this is a bug. I had some segments with a "0" in the "Num rows" column, but the "Records" tab in the segments modal actually showed a record.
4. I don't know what I did but at one point, while ingestion still worked, datasources were all marked as "unavailable" (yellow circle) and I had to restart all the containers to get it unstuck.
In the end, my current objective is to get a statistics from a bunch of urls (each url returns a flat json object).
The tasks for this were being triggered by NiFi (via Druid POST API). Speaking in DBMS terms, I'd like a row for each url in the same stats table (datasource in Druid terms, right?).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
Re: [I] Usability problems (druid)
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #13784:
URL: https://github.com/apache/druid/issues/13784#issuecomment-2537474391
This issue has been closed due to lack of activity. If you think that
is incorrect, or the issue requires additional review, you can revive the issue at
any time.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
Re: [I] Usability problems (druid)
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #13784:
URL: https://github.com/apache/druid/issues/13784#issuecomment-2475090413
This issue has been marked as stale due to 280 days of inactivity.
It will be closed in 4 weeks if no further activity occurs. If this issue is still
relevant, please simply write any comment. Even if closed, you can still revive the
issue at any time or discuss it on the dev@druid.apache.org list.
Thank you for your contributions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
Re: [I] Usability problems (druid)
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #13784: Usability problems
URL: https://github.com/apache/druid/issues/13784
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
Re: [I] Usability problems (druid)
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #13784:
URL: https://github.com/apache/druid/issues/13784#issuecomment-1928548003
This issue has been marked as stale due to 280 days of inactivity.
It will be closed in 4 weeks if no further activity occurs. If this issue is still
relevant, please simply write any comment. Even if closed, you can still revive the
issue at any time or discuss it on the dev@druid.apache.org list.
Thank you for your contributions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org