Good to finally hear about that :-)
Be patient, the first incubating release is quite hard regarding many legal
details. But focus on the technical scope, we'll support you with the rest.
On Thu, Apr 28, 2016 at 5:05 PM, DO YUNG YOON wrote:
> Hi folks.
>
> We have not discussed how and when we
I think this is a good first step. IMHO, releases need not be perfect but
make releases often and stick to a cadence to attract users and developers.
First step is for someone to volunteer as RM for this release. I have found
the Sqoop release docs [1] very easy to follow for a newbie.
[1] -
http
Hi folks.
We have not discussed how and when we are going to release our first
version.
I think we should discuss on scope of first release and list up issues that
need to be resolved.
Not sure how to start, but just wanted to open up thread so we can share
our opinion on release plan.
I am also fan of Neo4J’s web interface and I agree with JongWook's
opinion, think about the UI from the scratch.
I thought simply visualize graph structure could be done with simple
javascript work(maybe d3.js or something) since s2graph query has
"returnTree" feature that return entire tree that
When user query is provided, we are build RPC request(GetRequest, Scanner)
to fetch list of KeyValue from storage.
For query, I think mostly we only need bytes for rowKey(GetRequest), but
currently building rowKey, qualifier, value on Serializable is not
separated so we have to serialize qualifier
DOYUNG YOON created S2GRAPH-69:
--
Summary: Change IndexEdge's props data type.
Key: S2GRAPH-69
URL: https://issues.apache.org/jira/browse/S2GRAPH-69
Project: S2Graph
Issue Type: Sub-task
