[jira] [Deleted] (AVRO-3249) We grow small businesses with our effective Digital Marketing Strategies.
[ https://issues.apache.org/jira/browse/AVRO-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Thistlethwaite deleted AVRO-3249: --- > We grow small businesses with our effective Digital Marketing Strategies. > - > > Key: AVRO-3249 > URL: https://issues.apache.org/jira/browse/AVRO-3249 > Project: Apache Avro > Issue Type: Bug >Reporter: rahulsen >Priority: Trivial > > At Favfly, you can get all-in-one digital marketing solutions at an > unbeatable price. We excel to grow our customers' business and reach new > customers through our unique and tech-advanced marketing strategies. Consult > industry experts and choose the marketing plan perfect for your business. > [digital marketing services in kolkata|https://favfly.com/] > Over 100+ small businesses have chosen Favfly to grow their business. And you > can do it, too. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Issue Comment Deleted] (AVRO-2320) Generate accessors for field aliases (Java specific compiler)
[
https://issues.apache.org/jira/browse/AVRO-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Thistlethwaite updated AVRO-2320:
---
Comment: was deleted
(was: Hello,
I've been working on a php compiler (https://gitlab.com/Jaumo/phavroc) and had
a similar reflexion about handling aliases.
IMO, we could go a step further:
- Field aliases could trigger generation of both accessors (getter and setter)
with the same body but a different name.
- Named schema aliases could trigger generation of a child class (with the
alias name).
I don't know to what extent the current java compiler is supporting such
features, but here are some examples in php:
[https://gitlab.com/Jaumo/phavroc/issues/3.]
Regards.)
> Generate accessors for field aliases (Java specific compiler)
> -
>
> Key: AVRO-2320
> URL: https://issues.apache.org/jira/browse/AVRO-2320
> Project: Apache Avro
> Issue Type: Improvement
>Reporter: Denis Washington
>Priority: Major
>
> Currently, adding aliases to a field has no effect on the output class
> generated by SpecificCompiler. To make incremental code evolution easier, it
> would be beneficial if for each field alias, the compiler would generate
> corresponding a getter, setter and builder method with the aliased name that
> points to the same field. So for instance, a field like:
> {code:java}
> {
> "name": "firstName",
> "type": "string",
> "aliases": ["surname"]
> }{code}
> would be compiled to the following set of getter methods:
> {code:java}
> public String getFirstName() {
> return firstName;
> }
> public String getSurname() {
> return firstName;
> }{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AVRO-2041) set up gitbox integration
[ https://issues.apache.org/jira/browse/AVRO-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064801#comment-16064801 ] Chris Thistlethwaite commented on AVRO-2041: Sean, Just digging through GitBox tickets for INFRA and came across yours. When you're ready, please submit a ticket through https://issues.apache.org/jira/servicedesk/customer/portal/1/create/65 and we'll get you setup. > set up gitbox integration > - > > Key: AVRO-2041 > URL: https://issues.apache.org/jira/browse/AVRO-2041 > Project: Avro > Issue Type: Task > Components: community >Reporter: Sean Busbey >Assignee: Sean Busbey > > We got consensus back in may about [turning on gitbox > integration|https://lists.apache.org/thread.html/cdd8ba14c1bf8aca2d71d09862e9780f2dc46af414ed78b1e3fd9c56@%3Cdev.avro.apache.org%3E] > so do it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
