keith-turner commented on a change in pull request #108: Fix TODO for tour exercise URL: https://github.com/apache/fluo-website/pull/108#discussion_r149122758
########## File path: tour/exercise-1.md ########## @@ -198,8 +198,7 @@ u:http://oldnews.com/a23 uri hash a6c4d1f Now that you have data loading, create an observer that watches the reference status column. This observer should increment word counts when new content is -referenced and decrement word counts when content is dereferenced. The -observer should also delete the content when its dereferenced. +referenced and decrement word counts when content is dereferenced. The observer should also delete the content if zero URLs reference this one. If content's URL reference counts goes to zero and it was processed before, then its word counts should be decremented before deleting. Review comment: I have been trying to think of way to make this prose easier to understand and I could not. I think replacing the prose with a table would make this easier to understand. What do you think of the following? ```markdown Now that you have data loading, create an observer that watches the reference status column (*doc:refs*). This observer should take the following actions based on the values of the columns *doc:refs* and *doc:processed*. | doc:refs | doc:processed | Action | ------------ | ------------------- | ---------- | referenced | false | Increment word counts and set *doc:processed* to *true* | referenced | true | None | unreferenced | false | Delete content | unreferenced | true | Delete content and decrement word counts ``` @llvieira this is not the changes I was thinking of when I opened that issue (I'll update the issue to clarify). However that issue I opened was awful, it took me a while to figure out what I was thinking. Sorry! Anyway the changes you are making here are great because this is really confusing and needs to be improved. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
