Optic API support

[jmakeig]

• Plan builder to express queries in JavaScript
• Interoperability with other Java builders, such as cts:query or QBE
• Efficient handling of tuple results
• Map results to JavaScript/Node types and common I/O patterns (e.g. streams)
• Performance, especially for large record sets, millions of results, rather than pages as we assume with search results

[jmakeig]

@popzip The above is place-holder. Let’s figure out specifics.

[popzip]

@jmakeig Specifics...are there more specific requirements than the above + Client PRD + Optic PRD?

[popzip]

Just wanted to check this is still a post 9.0-1 task and won't make it into EA4 @wooldridge @jmakeig @ehennum

[ehennum]

Yes, this will require code generation for the builder, and the bucket for EA4 is full.

[popzip]

Okay thanks I thought there was something about code generation and couldn't remember the implication.

Also why is this an RFE not a task?

[grechaw]

Meaning @ehennum is there a server-side dependency still? @wooldridge is not 100% committed for EA-4 yet, from my initial researches into client api team.

[ehennum]

Yes, as noted above, the builder is generated. That requires work outside of Node.js