kou commented on code in PR #295:
URL: https://github.com/apache/arrow-site/pull/295#discussion_r1068676015


##########
use_cases.md:
##########
@@ -81,7 +83,8 @@ and [others]({{ site.baseurl }}/powered_by/) also use Arrow 
similarly.
 
 The Arrow project also defines [Flight]({% post_url 
2019-09-30-introducing-arrow-flight %}),
 a client-server RPC framework to build rich services exchanging data according
-to application-defined semantics.
+to application-defined semantics. Flight RPC is used by 
[UKV](https://unum.cloud/ukv)
+to exchange tables, documents, and graphs, between server application and 
client SDKs.

Review Comment:
   Apache Arrow project provides https://arrow.apache.org/powered_by/ as a page 
for introducing third-party projects including their use case. It's mentioned 
explicitly:
   
   > To add yourself to the list, please open a [pull 
request](https://github.com/apache/arrow-site/edit/master/powered_by.md) adding 
your organization name, URL, a list of which Arrow components you are using, 
and a short description of your use case.
   
   But other pages such as  https://arrow.apache.org/use_cases/ haven't 
discussed for the purpose explicitly. If you think that Apache Arrow project 
should use https://arrow.apache.org/use_cases/ for the purpose too, could you 
start a discussion on `[email protected]` mailing list?
   
   https://arrow.apache.org/community/
   
   > dev@ is for discussions about contributing to the project development 
([subscribe](mailto:[email protected]?subject=Subscribe), 
[unsubscribe](mailto:[email protected]?subject=Unubscribe), 
[archives](https://lists.apache.org/[email protected]))
   
   FYI: Apache Software Foundation provides suggested practices related to this 
topic: https://www.apache.org/foundation/marks/linking



-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to